-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Poly Phones
- Desk and IP Conference Phones
- Dialing SIP URL hangs up immediately on VVX 410

Create an account on the HP Community to personalize your profile and ask a question

03-16-2014 06:25 AM
My phone is currently connected to voip.ms SIP service. I am trying to dial into the TurboBridge SIP address to test the HD Voice connection. I have setup a contact record in the directory using the address sip:bridge@turbobridge.com. When I try to dial the contact my phone hangs up immediately. My understanding is that with SIP addresses that the device should try to reach out and connect directly with the SIP server on the other end. What would you recommend as a next step for troubleshooting?
I think this is the relevant part of the log:
0317012146|sip |2|493|SendCommand: reqDest 'turbobridge.com' isLync 0 isGRUU 0 isIP 0 useEffectiveProxy 1 0317012146|sip |1|493|SendCommand: isLync 0 isGRUU 0 isIP 0 useEffectiveProxy 1 0317012146|sip |1|493|CreateFailOverProxyList : Reg to Domain 'losangeles.voip.ms' nPort 5060 0317012146|sip |1|493|CreateFailOverProxyList : For INVITE Request nPort 5060 0317012146|sip |1|493|doDnsListLookup(udp): doDnsSrvLookupForARecordList for 'losangeles.voip.ms' port 5060 returned 1 results 0317012146|sip |1|493|doDnsListLookup(udp): result 0 '96.44.149.186' port 5060 isInBound 0 0317012146|sip |1|493|CreateFailOverProxyList : 'UDP Only' for 'losangeles.voip.ms' port 5060 IP 0 is '96.44.149.186' on udp port 5060 0317012146|sip |1|493|CreateFailOverProxyList : 'UDP Only' Add rest Total to Try 1 0317012146|sip |2|493|CreateFailOverProxyList : Exit 'UDP Only' lookup with 1 IP Addresses 0317012146|sip |2|493|CreateFailOverProxyList : IP 1 is '96.44.149.186' on udp port 5060 0317012146|sip |2|493|CTrans::InitRetrans for UA Client INVITE INVITE state 'callingTrying' Server 1 of 1 (0x40e45248) 0317012146|sip |2|493|CTrans::InitRetrans for UA Client Non-INVITE SUBSCRIBE state 'callingTrying' Server 1 of 1 (0x40e43aa8) 0317012146|sip |1|493|SipOnCommand: response 489,SUBSCRIBE 0317012146|sip |1|493|SipOnCommand: response 489,SUBSCRIBE matches user 1 of 2 '(removed)' 0317012146|sip |3|493|UA Client Non-INVITE SUBSCRIBE trans state 'callingTrying'->'completed' by 489 resp 10 timeout(0x40e43aa8) 0317012146|sip |2|493|CTrans:: SUBSCRIBE NonInv reTrans ALREADY stopped in 'completed' state at retryCount 2 code 489, timeout=10 (0x40e43aa8) 0317012146|sip |3|493|CStateSubscribeClient::OnEvResponse 489 for Idle 0317012146|sip |1|493|SipOnCommand: response 404,INVITE 0317012146|sip |1|493|SipOnCommand: response 404,INVITE matches user 1 of 2 '(removed)' 0317012146|sip |3|493|UA Client INVITE INVITE trans state 'callingTrying'->'completed' by 404 resp 65 timeout(0x40e45248) 0317012146|sip |2|493|CTrans:: INVITE InvTran reTrans ALREADY stopped in 'completed' state at retryCount 2 code 404, timeout=65 (0x40e45248) 0317012146|sip |1|493|Dialog 'id4f9824fa' State 'Trying'->'Terminated' 0317012146|sip |3|493|CStkCall::NewCallState 'Proceeding'->'Idle' (0xafd6c0),Control Channel(0) 0317012146|sip |2|493|SipOnEvCallNewState afd6c0,cc1538 10,Idle 0317012146|sip |3|493|GetRemotePartyAddress from 'To' 0317012146|sip |3|493|CStkCall::OnEvNewDest (0xafd6c0) new display '' user 'bridge%23(removed)' old 'From' new 'To' source 0317012146|sip |2|493|SipOnEvNewDest afd6c0,cc1538,sip:bridge#(removed)@turbobridge.com, 0317012146|sip |2|493|SipCallDrop afd6c0,cc1538 reason 6 0317012146|sip |2|493|CStkCall::Drop(reason = 6) (0xafd6c0) 0317012146|sip |3|493|CStkCall::NewCallState 'Idle'->'Idle' (0xafd6c0),Control Channel(0) 0317012146|sip |1|493|CStkCall::NewCallState Already Idle returning (0xafd6c0)
VVX 410 (standalone, no provisoining server)
UC Software 5.0.1.4068 / BootROM Software 5.2.1.3271
03-16-2014 08:29 AM
Hello ColinBowern,
pretty much like in your other unanswered post the server is this time sending you a 489 and a 404.
I suggest you work with your Provider for further troubleshooting.
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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

03-16-2014 11:00 AM
I'n not sure what you are experiencing. I susupec that it's either related to codec mismatch or proxy settings. My VVX-500 reaches Turbobridge without issue from a line registered with OnSIP.
Most significantly, I don't have an ouboard proxy setup. There's no need to force the media through an outbound proxy.
You'd get better info on exectly what's going on with a Wireshark capture of the SIP traffic.

03-16-2014 02:40 PM
My novice understanding was that SIP URLs are dialed directly from device to the SIP endpoint, not routed through my SIP provider. Is that correct?
I was afraid we would get into a wireshark trace - my home setup isn't passing through a managed switch at this point. I brought one with me from Canada but would need to source up a New Zealand power adapter for it. Is there any other way to get a dump of the SIP conversation to find out more?
03-16-2014 03:06 PM
Hello ColinBowern,
The community's VoIP => FAQ <= contains this post here:
Jan 19, 2012 Question: How to troubleshoot Polycom VoIP related Issues?
Resolution: Please check => here <=
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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

03-16-2014 03:56 PM
The 489 event was a red herring - misconfigured the line for the subscribe as feature event. The real issue is with the 404. Now that I have SIP header details through the debug logging I can reach out to my provider to find out why this is breaking.
03-17-2014 04:18 PM
Hello ColinBowern,
I did a quick test and I believe I can confirm your findings.
I would suggest, in order to clarify this, to raise this via your Polycom reseller in order to bring this to the attention of Polycom support.
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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN