Hi Todd,
Sounds like http://track.sipfoundry.org/browse/XX-7278 : Polycom does
not register when SIP domain != FQDN
The work-around is to go into each Polycom Line, and under Registration
change the Outbound Proxy Port from "5060" to blank.
-Paul
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Todd Hodgen
Sent: January 18, 2010 4:16 PM
To: [email protected]
Subject: [sipX-dev] FW: Polycom 430 doesn't work after update of
4.1.x viasipxconfig
I had a notice that an update was available on my server running
4.1.x I ran the update from sipxconfig. No issues with the update,
and it seemed to finish fine. I have one lingering issue from it
though. Calls come in and are answered by the Auto Attendant fine,
ITSP trunks seem to be working.
A polycom 430 phone that was working fine does not want to
register. It was set up with one line for the user, and the second line
for a speed dial number with presence. I've done the following -
Regenerated profile and started phone.
Regenerated server profiles
Created sipxmerge file after restarting phone. Only two entries
in the merge file - weird - a registration attempt of a speed dial
number for that extension with 405 method not allowed response
Removed speed dial from that phone
Saved Config
Rebooted phone
Still no registration
I've done a dig on my server, and it looks normal, returning
what I would expect for an A record. However, I get an error in the log
of the Polycom phone itself - 0117225147|sip
|4|01|doDnsListLookup(udp): doDnsSrvLookupForARecordList 'mydomain.com'
found no records.
It appears the Polycom phone is shutting down its SIP Stack.
What is weird is this all worked prior to the update, and my
soft clients still work, but none of my polycoms. Anyone seen any
issues with Polycom with this update? I see one JIRO issue raised, but
it appears to be with HA configurations. I'm tempted to re-install from
ISO to see if the problem goes away, using the most recent unstable ISO,
unless someone needs some specific testing done to try and isolate a
potential problem.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
