cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1428
Views
5
Helpful
11
Replies
Highlighted
Beginner

SipEdge Acano Deployment

I have testing on a Develop network for Cisco meeting server single split deployment. I want to use SipEdge feature on Edge Server. Is there anyone have the experience about SipEdge configuration? I have read the deployment doc for single split, but I think the doc is not clear about outbound dial rules with traversal. 

Please help me to share the sample configuration for SipEdge. 

3 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted

Hi Erwin,

 

Your sipedge and call bridge configuration should look like that. 

make sure you do the following and its must.

 

1. SIP Edge always have 2 intefaces "a" and "b". your NATed interface should be the first interface "a" of Edge server. 1st interface should be your default interface reaching internet. and you manually add static route to reach callbridge via 2nd interface "b".

2. sipedge "a" interface should be listening to 5061 and "b" interface should be any port other than 5061. let say 3061 as per below example.

3. SIP Edge should be using public certificate and external DNS records should be pointing to its 1st interface.

4. SIP edge must trust callbridge certificate.

5. callbridge must trust sipedge certificate.

6. then you need outbound rules in GUI and API modification of that rule to use SIP Edge. 

Lync Federation or SIP Traversal OutboundDialplanRules need API modification with callRouting=Traversal and Outbound Encryption should be=YES

this is done in CMS core.

 

xxxxxxxxxx> sipedge
Enabled : true
Public interface : a:5061 (NAT address 88.85.22.111)
Private interfaces : b:3061
Certificate : sip.crt
Key : sip.key
Trusted certificates : callbridge.crt

xxxxxxxxx> callbridge
Listening interfaces : b a
Preferred interface : b
Key file : callbridge.key
Certificate file : callbridge.cer
Address : none
CA Bundle file : comodo.pem
Edges
Address : 10.1.101.15:3061
Trusted certs : sip.crt

 

################ SAMPLE CONFIG - SPLIT DEPLOYMENT ###############

##### SIP EDGE CONFIG ---CMS EDGE ##############

sipedge private b:3061
sipedge public a:5061
sipedge public-ip 88.85.22.111
sipedge certs sip.key sip.crt callbridge.crt
sipedge enable

 

## CALLBRDIGE CONFIG- CMS CORE ###########
callbridge trust edge sip.crt
callbridge add edge 10.1.101.15:3061

 

HTH

AMMAR

View solution in original post

Highlighted

No it doesnot require any license.

make a test call and show me logs. let me see if Callbridge is actually forwarding the call to SIP Edge or not.

also take snapshot of your outbound rules and SIP edge configuration.

View solution in original post

Highlighted
Beginner

Many thanks ammar.

It have been solved. it was TURN and certificate issue..and some SIP EDGE config issue. 

 

 

View solution in original post

11 REPLIES 11
Highlighted
Participant

let me break it down to make it simple for you. Remember these key points.

  1. SIPEDGE must have public signed Certificate
  2. _sipfederationtls._tcp.domain.com points to SIPEDGE public IP for Lync/ microsoft Skype for business calls.
  3. _sips._tcp.domain.com points to SIPEDGE public IP for SIP Calls.
  4. It only listens on port TCP 5061 for Lync and SIP Calls
  5. callbridge and sipedge must trust each other certificates.

Lync Federation or SIP Traversal OutboundDialplanRules need API modification with callRouting=Traversal and Encryption=YES

 

 

Please mark as answered and rate if helpful.

Highlighted

How about trunk from core to edge?

Highlighted

These are 2 independent things. Loadbalancer trunk and SipEdge.

trunk from core to edge is only require if you are using Loadbalancer on EDGE for xmpp traffic which is used for CMA app / WEBRTC.

sipedge component on Edge Server doesn't depend on that trunk. its only to process calls not xmpp traffic for CMA or WEBRTC.

 

HTH

AMMAR

Highlighted

Hi Ammar saood,

 

Many thanks for you're information. I will trying again, and will update soon

 

Highlighted

Still confuse about sipedge, is there anyone have sample config about sipedge. And how to test sip uri outbound dial, is there any sip online available to be tested ? 

 

Highlighted

Hi Ammar,

Lync Federation or SIP Traversal OutboundDialplanRules need API modification with callRouting=Traversal and Encryption=YES

Above api configuration is in cms core server right?
Highlighted

Hi Erwin,

 

Your sipedge and call bridge configuration should look like that. 

make sure you do the following and its must.

 

1. SIP Edge always have 2 intefaces "a" and "b". your NATed interface should be the first interface "a" of Edge server. 1st interface should be your default interface reaching internet. and you manually add static route to reach callbridge via 2nd interface "b".

2. sipedge "a" interface should be listening to 5061 and "b" interface should be any port other than 5061. let say 3061 as per below example.

3. SIP Edge should be using public certificate and external DNS records should be pointing to its 1st interface.

4. SIP edge must trust callbridge certificate.

5. callbridge must trust sipedge certificate.

6. then you need outbound rules in GUI and API modification of that rule to use SIP Edge. 

Lync Federation or SIP Traversal OutboundDialplanRules need API modification with callRouting=Traversal and Outbound Encryption should be=YES

this is done in CMS core.

 

xxxxxxxxxx> sipedge
Enabled : true
Public interface : a:5061 (NAT address 88.85.22.111)
Private interfaces : b:3061
Certificate : sip.crt
Key : sip.key
Trusted certificates : callbridge.crt

xxxxxxxxx> callbridge
Listening interfaces : b a
Preferred interface : b
Key file : callbridge.key
Certificate file : callbridge.cer
Address : none
CA Bundle file : comodo.pem
Edges
Address : 10.1.101.15:3061
Trusted certs : sip.crt

 

################ SAMPLE CONFIG - SPLIT DEPLOYMENT ###############

##### SIP EDGE CONFIG ---CMS EDGE ##############

sipedge private b:3061
sipedge public a:5061
sipedge public-ip 88.85.22.111
sipedge certs sip.key sip.crt callbridge.crt
sipedge enable

 

## CALLBRDIGE CONFIG- CMS CORE ###########
callbridge trust edge sip.crt
callbridge add edge 10.1.101.15:3061

 

HTH

AMMAR

View solution in original post

Highlighted

Hallo Ammar

 

Is the edge server need active license ? I have config as your suggest, sipedge seems not forwarding the call. I collect pcap and found "header not terminated by empty line (crlf)" after sip.

Highlighted

No it doesnot require any license.

make a test call and show me logs. let me see if Callbridge is actually forwarding the call to SIP Edge or not.

also take snapshot of your outbound rules and SIP edge configuration.

View solution in original post

Highlighted
Beginner

Many thanks ammar.

It have been solved. it was TURN and certificate issue..and some SIP EDGE config issue. 

 

 

View solution in original post

Highlighted
Beginner

Many thanks ammar.

It have been solved. it was TURN and certificate issue..and some SIP EDGE config issue. 

 


@Erwinnugros1 wrote:

I have testing on a Develop network for Cisco meeting server single split deployment. I want to use SipEdge feature on Edge Server. Is there anyone have the experience about SipEdge configuration? I have read the deployment doc for single split, but I think the doc is not clear about outbound dial rules with traversal. 

Please help me to share the sample configuration for SipEdge.