One X communicator and SIP

[Jsaunde7]

In the process of moving from T1s to SIP And having issues with getting our soft phones(communicator and one-x agent) to work in our test environment...I've setup the extension in session manager and also changed settings from h.323 to Sip in communicator and also updated extension phone type from 9630 to 9630SIP and when I try to login to communicator getting login attempt failed/unsuccessful. Any help much appreciated

 

[fondog2]

Jsaunde7,
Couple of things to keep in mind. One you do not build the stations in CM, you build them in Session Manager and it pushes them down. Second you need to convert your entity links to TLS for the PPM data and encryption for off site users. Third Use a TLS port od 6061 instead of 5061. We had several issues trying to use 5061. Lastly all calls will be looking at the lowest numbered signaling group as first choice. It is how the algorithm is designed by Avaya. Once you login verify your buttons work on the application. If they don't then it isn't passing the PPM data. Hope this helps.

 

[Jsaunde7]

All our stations were previously built in CM Simce were converting to sip. Will this be an issue since stations are already in CM. Think we're currently using TCP in our test environment before me move to production. We don't have offsite users just remote workers who sometimes login with Remote Desktop to access there PC.

 

[fondog2]

I would remove them one at a time then build in Session Manager. They are so much fun to build. SIP needs to be TLS.