wadelowe Report post Posted 11/29/2011 08:52 PM I am upgrading my current dialogic hardware system to VoIP with HMP. I have no issues registering and dialing into the system. However when I load numbers into the loader it will begin dialing and no calls are placed. I receive the following from the ShoreTel Switch: ------------------------------------------------------------ INVITE sip:137@198.168.1.95 SIP/2.0 From: <sip:ivr@198.168.1.96>;tag=e2f16b8-0-13c4-50022-1c10-2ee49c59-1c10 To: <sip:137@198.168.1.95> Call-ID: dfd8520-0-13c4-50022-1c10-3daf203-1c10 CSeq: 1 INVITE Via: SIP/2.0/UDP 198.168.1.96:5060;branch=z9hG4bK-1c10-6da07b-6696166e Max-Forwards: 70 Supported: replaces Contact: ivr@198.168.1.96<sip:ivr@198.168.1.96> Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, INFO, REFER, NOTIFY Allow-Events: refer Content-Type: application/sdp Content-Length: 225 v=0 o=Dialogic_SIP_CCLIB 234718496 234718497 IN IP4 198.168.1.96 s=Dialogic_SIP_CCLIB i=session information c=IN IP4 198.168.1.96 t=0 0 m=audio 49152 RTP/AVP 0 8 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 -------------------------------------------------------------- SIP STACK ERROR:Parse Error in Contact Header due to error in parsing address-spec Using Wireshark the INVITE is sent and never returned, Voiceguide/HMP will try several times and then fail on timeout. It appears that ShoreTel is failing to parse the Contact Header and then drops the packet with no response. I have attached a wireshark trace of a VG call and an XLite call, the VG does not work and the XLite works great, from the same server. VGOutboundCall.zip Share this post Link to post
SupportTeam Report post Posted 11/30/2011 02:02 AM In the VoiceGuide trace the first INVITE captured has: From: <sip:198.168.1.96:5060>; tag=...... Contact: <sip:198.168.1.96:5060> and the second (and following) INVITEs captured have: From: <sip:ivr@198.168.1.96>; tag=...... Contact: ivr@198.168.1.96<sip:ivr@198.168.1.96> Was the CallerID of the outbound calls not set on first outbound call attempt, but set to ivr@198.168.1.96 for second outbound call attempt? Can you please confirm which Service Update of HMP you are using? Share this post Link to post
wadelowe Report post Posted 11/30/2011 04:46 AM The trace log that I sent was from one dialer attempt with no settings changes. It will invite several times in the first few seconds after I click the "load numbers" button in the dialer. I am using HMP3.0 SU310. Share this post Link to post
SupportTeam Report post Posted 11/30/2011 05:03 AM Are you setting the CallerID on the outbound calls? (using the <CallerID> field in the XML formatted Call Options)Please download this version of VoiceGuide v7: [old link removed]then stop the VoiceGuide service, install new version over the top of the existing version, and then try making outgoing calls again.Try setting the <CallerID> to be:<CallerID>ivr@198.168.1.96</CallerID>and if that does not work then try using this expression in the Call Options:<CallerID>From: <sip:ivr@198.168.1.96></CallerID>Please post VoiceGuide's ktTel traces as well as the WireShark traces that capture outgoing calls. Share this post Link to post
wadelowe Report post Posted 12/01/2011 04:30 PM The link is not working. Share this post Link to post
wadelowe Report post Posted 12/01/2011 04:32 PM The <CallerID> option is set and was set on all the calls attempted: It is set as <CallerID>ivr@198.168.1.96</CallerID> I will try the other syntax and report back. Share this post Link to post
SupportTeam Report post Posted 12/01/2011 08:56 PM That link should be working again now (looks like previously it was taken down after 24 hours). The new CallerID Syntax that specifies the full "From:" line can only be used correctly with the new version. Share this post Link to post
wadelowe Report post Posted 12/02/2011 02:22 PM I installed the new version with the CallerID as <CallerID>ivr@198.168.1.96</CallerID> and it works now. It also works with CallerID as <CallerID>From: <sip:ivr@198.168.1.96></CallerID> That appears to have resolved the issue. Thanks. Share this post Link to post
SupportTeam Report post Posted 12/03/2011 04:36 AM OK, thanks for letting us know that it works fine now, Share this post Link to post