I am new to this forum and am having a fit getting a Soundstation IP 6000 to register with an Avaya Session Manager. I have successfully registered them with Avaya Session Enablement Servers in the past, but no luck her. I have App Notes from Avaya that I have followed to no avail. I was able to get an X-Lite soft client to register successfully. Any assistance would be greatly appreciated. I am attching the App Note that i am using.
Solved! Go to Solution.
welcome to the Polycom Community.
How about you tell us a bit more about what you have done to the SSIP6000 and what issue you are having?
I am trying to get a new Soundstation IP6000 to register with an Avaya Session Manager 6.x. I have followed all documentation that i can find including the Avaya Application Note, but I can't get the phone to register. I have used the same setup and registered softphones without issue. I have upgraded to the latest firmware on the IP6000 as well. I am attaching the App Note that I have been using.
so what is failing? Post a screenshot of your line registration.
How do I obtain that screenshot? I am currently not on site, but I can get to the web interface through VPN if there is any useful information there.
Thanks for your assistance.
The only thing I see on the phone when I go to the status screen is:
Line 1: 9850 (Not registered)
10.0.100.17 (Not registered) 0
This is the IP Address of Server 1 which is the Session Manager.
what sort of changes did you make to the Phone?
Via the Web Interface or via provisioning from a Server?
What Software Version are you running?
I have tried settings from the phone and from the web interface. Most recently, I only set the syslog server (based on App Notes) to the Session Manager (SM) IP address from the phone itself.
From the web interface, I set the Server 1 address to the Session Manager, port to 5060 and transport yo UDPonly. I set the local port to 5060. I set Line 1 name, label, etc to the phone's extension and I ahve tried to set the address to ext@domain as well as ext@SM IP Address, with authentication name as the extension and the password as the user's password that I created on the SM
the issue in your case is most likely caused by the combination of changes made to the Phone via the GUI and the Web Interface.
Changes made via the guide take precedence over changes made to the Web Interface.
You have so far not yet responded what Software Version you are using and what method of provisioning of the Phone you have used.
We also now have a public boot server, if you wish to use it instead to upgrade your phone(s). Instructions are listed on the main page:http://voipt2.polycom.com
In your case I recommend to do the following in order to upgrade the Unit to the latest available UCS 3.3.1 rev F Build and BootROM 4.3.0:
Once the Phone reboots press Setup whilst the countdown is being shown
The Phone will now attempt to Provision itself from the public Polycom Server.
If the above fails due Firewall restrictions please liaise with your local IT Administrator Team and/or follow => this <= guide on how to setup a standalone FTP provisioning server.
Once the Phone has booted and upgraded please change settings via the Admin Menu on the Phone (Password 456) or the Web interface (Username Polycom, Password 456)
On the Phone:
· (3) Settings
· (2) Advanced
· Password 456
· (1) Admin Settings
· (2) Line Configuration
· Scroll down to select Line 1
Usually for a SIP Switch you add within the Lines Menu the following values:
Address = the Extension/DDI/Username usually assigned to the Phone
Auth User ID = the Extension/DDI/Username usually assigned to the Phone
Auth Password = the DDI Password usually assigned to the Phone
Label = can be used to show the Phones DDI or Name when idle
Within the Server 1 Settings Submenu add the IP address of the SIP Switch in the Address Field
No other entries are usually needed.
The Phone may reboot after changing Values.
For further support please contact your Polycom Reseller.