Polycom 3XX Redirect on Register Message

[Anonymous]

I was expecting the 4.0.1B UCS software to properly handle RFC 3261 SIP 3XX redirect messages.

I am properly inserting the updated CONTACT header on the return SIP message, and yet the Soundpoint IP phones do not attempt to re-register to the new server.

Has anyone worked on this in the past?  Is there a way to accomplish the redirects as I would like to?

[SteffenBaierUK]

Hello Jo,

welcome to the Polycom Community.

The UCS 4.0.1 Admin Guide list's all the supported 3XX Scenarios on page 552:

The Feature Descriptions & Technical Notifications => here <= and the UCS Admin Guide contain explanations regarding these functionalities.

You have not posted any configuration changes that you made in order to support this feature so other users won't be able to advise you on anything.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

I did see that and that was encouraging.  However, this doesn't seem to work properly when the message type is REGISTER.

Here's the logs showing the packets.  I simply never see an attempt to use the CONTACT header's URI to register to a new server.

0904230628|sip |0|03|>>> Data Send to 108.x.x.x:5060
0904230628|sip |0|03| REGISTER sip:proxy.server.com SIP/2.0
0904230628|sip |0|03| Via: SIP/2.0/UDP 192.168.0.136;branch=z9hG4bK4a0c3ae66F3BE5C5
0904230628|sip |0|03| From: "2401" <sip:123@proxy.server.com>;tag=A3A81E99-44159C10
0904230628|sip |0|03| To: <sip:123@proxy.server.com>
0904230628|sip |0|03| CSeq: 1 REGISTER
0904230628|sip |0|03| Call-ID: 4bc7109c-5a0a032b-60bd8332@192.168.0.136
0904230628|sip |0|03| Contact: <sip:123@192.168.0.136>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
0904230628|sip |0|03| User-Agent: PolycomSoundPointIP-SPIP_331-UA/4.0.2.11307
0904230628|sip |0|03| Accept-Language: en
0904230628|sip |0|03| Max-Forwards: 70
0904230628|sip |0|03| Expires: 3600
0904230628|sip |0|03| Content-Length: 0
0904230628|sip |0|03|
0904230628|sip |2|03|adjustRetransWhenTimerCreated UA Client Non-INVITE REGISTER state 'callingTrying' timeout=65 (0x95d99fd0)
0904230628|sip |3|03|CCallNoCall::NewCallState 'Register'->'Register' (0x95d71c10)
0904230628|sip |3|03|CCallNoCall::NewCallState 'Register'->'Register' (0x95d71c10)
0904230628|sip |3|03|RegClient:RegClient expire 66 overlap 0
0904230628|sip |0|03|<<<Packet Received
0904230628|sip |0|03| SIP/2.0 301 Moved Permanently
0904230628|sip |0|03| Via: SIP/2.0/UDP 192.168.0.136;branch=z9hG4bK4a0c3ae66F3BE5C5;received=216.x.x.x
0904230628|sip |0|03| From: "2401" <sip:123@proxy.server.com>;tag=A3A81E99-44159C10
0904230628|sip |0|03| To: <sip:123@proxy.server.com>;tag=0e4aeaba66d05b87bb14042b41785dad.b4dc
0904230628|sip |0|03| CSeq: 1 REGISTER
0904230628|sip |0|03| Call-ID: 4bc7109c-5a0a032b-60bd8332@192.168.0.136
0904230628|sip |0|03| Contact: 108.x.x.x:5060
0904230628|sip |0|03| Server: Proxy v3.1
0904230628|sip |0|03| Content-Length: 0
0904230628|sip |0|03|
0904230628|sip |1|03|SipOnCommand: response 301,REGISTER
0904230628|sip |1|03|SipOnCommand: response 301,REGISTER matches user 1 of 1 '123'
0904230628|sip |3|03|UA Client Non-INVITE REGISTER trans state 'callingTrying'->'completed' by 301 resp 10 timeout(0x95d99fd0)
0904230628|sip |2|03|CTrans:: REGISTER NonInv reTrans ALREADY stopped in 'completed' state at retryCount 0 code 301, timeout=10 (0x95d99fd0)
0904230628|sip |1|03|Dialog 'ide899ae1a' State 'Trying'->'Confirmed'
0904230628|sip |1|03|Dialog 'ide899ae1a' State 'Confirmed'->'Terminated'
0904230628|sip |2|03|CStkDialog::CStkDialog SetAddressLocal Config '2401' <123@proxy.server.com:0>
0904230628|sip |2|03|CStkDialog::CStkDialog AddressLocal set to Config
0904230628|sip |3|03|CStkDialog::SetAddressLocal localTag set to ''
0904230628|sip |3|03|CStkDialog::SetAddressLocal new address added of 1
0904230628|sip |2|03|CStkDialog::CStkDialog TAG '2D2AD8A8-D2039F97' generated
0904230628|sip |2|03|CStkDialog::CStkDialog local addr '2401' <123@proxy.server.com:0> Tag '2D2AD8A8-D2039F97'
0904230628|sip |2|03|CStkDialog::CStkDialog exit 0x95d65964 local list size 1
0904230628|sip |2|03|CStkDialogList::CreateDialogObject localTarg usr '123'
0904230628|sip |3|03|Reg UAC Response: code 301 new m_nExpire 118 m_nOverlap 0 ticks Trans 0x95d99fd0
0904230628|sip |3|03|Reg UAC Response: code 301 new Address 'sip:108.x.x.29:5060'

The last line:

Reg UAC Response: code 301 new Address 'sip:108.x.x.29:5060'

would seem to indicate that the Polycom is aware it's supposed to redirect itself, but that simply never happens.

Couldn't seem to see any settings that would influence how the 300-302 messages are handled.

[SteffenBaierUK]

Hello Jo,

if you are sure that you followed the fail over guide and programmed the phone accordingly and are seeking support please contact your Polycom reseller to bring this to the attention of the Polycom support team in your region.

Alternatively you are more then welcome to wait for other community members to help you troubleshooting your setup.

Best Regards

Steffen Baier