SIP Trunks

[td1019]

IN CM 5.2.1 can you have SIP trunks straight to a carrier and not use SES? Or do you have to go through SES? I have an A,B ESS CM solution with one SES server for linking MM only. The SES would be a single point of failure for the SIP trunks unless I could bypass it and go from CM straight to SBC of the carrier.

 

[joesena]

The main issue is that you can't use any authentication by using the CM for SIP termination. If you can get around that, you can likely get it to work.

 

[montyzummer]

plus a direct sip trunk into cm can only be set to TLS or TCP transport method so you may struggle to find a carrier with these settings for delivery.

APSS (SME)
ACSS (SME)

 

[td1019]

what if the carrier is putting their own SBC onsite not sure what brand SBC it is.

 

[redphone]

Going directly from CM to an SBC without the SES is a supported solution. There are Application Notes on Avaya's website illustrating this.

Here are a couple of examples:

https://devconnect.avaya.com/public/download/dyn/CM521-AP-Sprint.pdf

http://devconnect.avaya.com/public/download/dyn/ACM521SBCXC.pdf