@Paul McGurn wrote: I can't relate to 7.1, but can say I was able to register these to 8.6. I also ran into the auth issues though. One thing that will make your life easier, if you aren't doing it already, is using the web UI for the IP7000. Simply browse to the IP address of the SIP phone, and log in. The default credentials are username:Polycom , password:456. Once your'e in there, verify: SIP Tab Outbound proxy = CUCM IP Outbound proxy port = 5060 Outbound proxy protocol = UDPOnly Server 1 Address = CUCM IP Port = 5060 Protocol = UDPOnly You can fill in server 2 with the other CUCM IP if you're running a cluster. Server 1 should be subscriber, if so (per Cisco best practices on registration). Line Tab Display Name = Whatever you want Address = CUCM DN you assigned to the phone Authentication User ID = Case-sensitive user ID you are tying the phone to Authenticatio password = The Digest password associated with the above user Label = I set this to match the DN, not sure if it matters Type = Private Third party name = DN@, example email@example.com I set server 1 and server 2 info to match the SIP info, but I set Register to 1. Notes I didn't have to tie the SIP phone to the LDAP user I created for it You can't use the same digest user on more than one SIP phone (at least in our version, when we tried to) This config worked for us on Polycom IP7000's, IP6000's, and IP5000's Setting up the digit maps was an utter pain. Polycom has a decent default for US, but it has holes, and if users expect to take the phone off-hook, and then dial, the digit maps need to be perfect in order to provide a good user experience. The headache we went through to get this working outweighed the additional costs of Cisco's 7937G (which is a Polycom IP7000 running SCCP), so we're now exclusively deploying 7937G's instead of these. This configuration reference just helped me register the same phone, and I couldn't find this information (easily) anywhere on Polycom's site. Kudos and thank you!
... View more
Good Morning, Did you figure this out? I am running into an issue much like this with my TSP drivers. SelsiusTSP::CtiLineInServiceEventWorker() *ERROR* Could not find line handle 0x00000001
... View more