We are trying to run a proof of concept pilot with Avaya Communicator on Windows 7 devices - we are using Session Manager / CM 6.4 with H323 endpoints.
To keep things simple we initially just want to log in a test SIP user that we've created in Session Manager rather than dual-registration with any H323 phones / extensions.
When we try and log the test SIP user in we get the message "Incorrect extension or password" no matter what we try. We only have a single SIP user created in Session Manager (the test user) - I am therefore wondering if there is some config missing within Session Manager user that is causing the problem.
As usual, the Avaya documentation isn't particularly helpful in getting this set up.
Anybody any ideas?
Thanks in anticipation.
**Update
When doing a traceSM in System Manager, when connecting with TCP I can see the registration attempt failing with a 403 "Forbidden" message, when using TLS I can see a "480 SIPS Not Allowed" message.
To keep things simple we initially just want to log in a test SIP user that we've created in Session Manager rather than dual-registration with any H323 phones / extensions.
When we try and log the test SIP user in we get the message "Incorrect extension or password" no matter what we try. We only have a single SIP user created in Session Manager (the test user) - I am therefore wondering if there is some config missing within Session Manager user that is causing the problem.
As usual, the Avaya documentation isn't particularly helpful in getting this set up.
Anybody any ideas?
Thanks in anticipation.
**Update
When doing a traceSM in System Manager, when connecting with TCP I can see the registration attempt failing with a 403 "Forbidden" message, when using TLS I can see a "480 SIPS Not Allowed" message.
Comment