We have a VVX 300 with 5.0.0 UC software that inserts a Record-Route header with the IP of its outbound proxy in a 180 Ringing message in response to all inbound INVITE messages. This causes issues with the outbound proxy that ends up sending messages to itself, causing a teardown in the call. I can find nothing in the software release notes that mention this as a known issue. Any ideas on why the phone would do this? Below is a SIP message with the odd header.
U 2014/07/08 02:35:07.029821 192.168.55.102:5060 -> 192.168.55.1:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 192.168.55.1:5060;branch=z9hG4bK-963-F723D5CF-76d9957bf3b3423052650a3331cd3f93.
Via: SIP/2.0/UDP <outside_proxy_ip>:5060;branch=z9hG4bKv20sg500eosg3cd0h7n1.1.
From: "NELSON" <sip:<cell_phone>@192.168.55.102;user=phone>;tag=1877600395-1404786906778-.
To: "Customer" <sip:<vvx300_phone>@<proxy_fqdn>;adtnpxyid-1i5f8543=k63hid>;tag=C36801C6-69AF330F.
CSeq: 166300494 INVITE.
welcome to the Polycom Community.
What is the exact Software Version as UCS 5.0.0 is rather old and you should check UCS 5.0.2 instead.
In addition what call server are you using?
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
Is 22.214.171.12474 what you are looking for?
The upstream component is an Acme SBC that is protecting a Broadsoft softswitch infrastructure.