Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Messaging (http://support.avaya.com/forums/forumdisplay.php?f=4)
-   -   CMM 6 using SIP trunks (http://support.avaya.com/forums/showthread.php?t=379)

ahartoch 09-27-2010 08:16 AM

CMM 6 using SIP trunks
 
Hi,

Has anybody deployed a CMM embedded 6 using SIP trunks? If yes, is it neccesary to create 2 different signalling groups to session manager using different ports (5060 and 6060)?

Regards,
Alex

sunilkumarv 09-29-2010 06:02 AM

Refer the implementation doc on support website.https://support.avaya.com/css/P8/documents/100089467It is assumed that you have created an entity for Session Manager in System Manager.Entity link between Session Manager and other SIP entities.You must create entity links between:• Communication Manager Messaging and Session Manager• Communication Manager Feature Server and Session Manageror Communication Manager Evolution Server and Session Manager

ahartoch 09-29-2010 07:23 AM

We have followed the document you are mentioning, and it's not clear at all. The document states to create an entity link over a different port if it's a CMM embedded lets say 6060. However do we need to establish an additional signalling group over port 6060 between CM and SM?

Morevover, is there a way to obtain SIP traces on the SIP agent within CMM to analyze?

Alex

ahartoch 09-30-2010 01:41 PM

The documentation, does not make a clear statement whether an additional signaling group has to be made over a different port when connecting to SM. Finally, what we have setup until now is, one signaling group between CM and SM over port 5060. We have then created 2 sip entity links in SM: One over port 5060 and one over 6060. We have also added port 6060 on the switch link administration.

What is very confusing to understand is, how can the signaling group between SM and CM be setup over port 5060, yet the calls come in through port 6060 and the call get's routed to the CMM.


Alex


All times are GMT -7. The time now is 06:04 AM.