SenorWatsonSan
Vendor
Hello all,
Hoping someone can shed some light.
UCx EMetrotel PBX behind Sonicwall Firewall.
Took over account from a hosted VoIP provider which had depolyed Polycom Soundpoint 335 phones.
Onsite Polycom phones are working fine.
Discovered that two users were remote.
Had IT people port-forward SIP registration and RTP ports.
I can register/make calls OK using my test phones: XLite Softphone and a Yealink T23 Deskphone.
Calls in/out are ok and two-way audio is good while using Xlite and Yealink.
The last piece of the puzzle for those two phones was adding STUN server info.
Before adding STUN, XLite was only getting one-way audio, and Yealink wasn't registering at all.
I can't find anything related to STUN in the web config of the Polycom 335.
There is a NAT section, but that seems to be for hard-setting the public static of the remote location, which won't work since the remote users are sitting on consumer-grade internet connections with dynamic addresses.
I thought I found the key when I found the following config parameters in the documentation for UC 4.1.1 Admin guide (Page 530):
tcpIpApp.ice.stun.server=
tcpIpApp.ice.stun.udpPort=
I added "stun.l.google.com" on port "19302" (this being the same server/port that worked on Xlite and Yealink).
The phone itself, however, was still at 4.0.4, and adding it to the config file of the Polycom produced the following log entries:
0812143737|cfg |4|03|Prm|reg-and-device-basic.cfg: Unknown parameter "tcpIpApp.ice.stun.server" found, ignoring,
0812143737|cfg |4|03|Prm|reg-and-device-basic.cfg: Unknown parameter "tcpIpApp.ice.stun.udpPort" found, ignoring,
So, despite the fact that this phone somehow was working when it was configured by the hosted VoIP and should be doable as-is, I upgraded the phone from 4.0.4 to 4.1.1. My hope was to add this STUN functionality that I shouldn't really have needed in the first place, but made things work on XLite and Yealink phones.
The log entries that the STUN parameters were being ignored are now gone, but this phone still isn't registering, and the issue is the same. I can see in Wireshark (captured from the UCx NIC) that the phone system is receiving the registration request, and sending back "401 Unauthorized". However, a Wireshark capture from the other end, tapped into the Polycom's connection, shows that NONE of the "401 Unauthorized" messages make it back to the Polycom. This was the same behavior with the Yealink phone until I added STUN info.
So, this is a Polycom configuration issue related to Network setup.
Note: DNS is definitely OK, as the phone is syncing SNTP to pool.ntp.org using 8.8.8.8 as DNS.
Thanks for your time, now please tell me exactly how I have overthought this and there's a simple checkbox somewhere on the Polycom that will make this problem go away.
Hoping someone can shed some light.
UCx EMetrotel PBX behind Sonicwall Firewall.
Took over account from a hosted VoIP provider which had depolyed Polycom Soundpoint 335 phones.
Onsite Polycom phones are working fine.
Discovered that two users were remote.
Had IT people port-forward SIP registration and RTP ports.
I can register/make calls OK using my test phones: XLite Softphone and a Yealink T23 Deskphone.
Calls in/out are ok and two-way audio is good while using Xlite and Yealink.
The last piece of the puzzle for those two phones was adding STUN server info.
Before adding STUN, XLite was only getting one-way audio, and Yealink wasn't registering at all.
I can't find anything related to STUN in the web config of the Polycom 335.
There is a NAT section, but that seems to be for hard-setting the public static of the remote location, which won't work since the remote users are sitting on consumer-grade internet connections with dynamic addresses.
I thought I found the key when I found the following config parameters in the documentation for UC 4.1.1 Admin guide (Page 530):
tcpIpApp.ice.stun.server=
tcpIpApp.ice.stun.udpPort=
I added "stun.l.google.com" on port "19302" (this being the same server/port that worked on Xlite and Yealink).
The phone itself, however, was still at 4.0.4, and adding it to the config file of the Polycom produced the following log entries:
0812143737|cfg |4|03|Prm|reg-and-device-basic.cfg: Unknown parameter "tcpIpApp.ice.stun.server" found, ignoring,
0812143737|cfg |4|03|Prm|reg-and-device-basic.cfg: Unknown parameter "tcpIpApp.ice.stun.udpPort" found, ignoring,
So, despite the fact that this phone somehow was working when it was configured by the hosted VoIP and should be doable as-is, I upgraded the phone from 4.0.4 to 4.1.1. My hope was to add this STUN functionality that I shouldn't really have needed in the first place, but made things work on XLite and Yealink phones.
The log entries that the STUN parameters were being ignored are now gone, but this phone still isn't registering, and the issue is the same. I can see in Wireshark (captured from the UCx NIC) that the phone system is receiving the registration request, and sending back "401 Unauthorized". However, a Wireshark capture from the other end, tapped into the Polycom's connection, shows that NONE of the "401 Unauthorized" messages make it back to the Polycom. This was the same behavior with the Yealink phone until I added STUN info.
So, this is a Polycom configuration issue related to Network setup.
Note: DNS is definitely OK, as the phone is syncing SNTP to pool.ntp.org using 8.8.8.8 as DNS.
Thanks for your time, now please tell me exactly how I have overthought this and there's a simple checkbox somewhere on the Polycom that will make this problem go away.
