jannies Posted June 6, 2012 Report Share Posted June 6, 2012 Hi We have been testing CSTA MakeCall for some time and all of a sudden we are receiving an error "Invalid header(s): To" from our sip Gateway device. It seems the domain gets appended twice behind the number to be dialed. We have been testing this functionality for weeks and this problem started happening yesterday. Please see partial call log below: [5] 2012/06/06 11:56:21: SIP Tx udp:192.168.0.19:5060: INVITE sip:0718961395@192.168.0.19;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.0.12:5060;branch=z9hG4bK-23ddcf1f2f619a06a96c113862f8dc5b;rport From: <sip:8025@192.168.0.12;user=phone>;tag=687137098 To: <sip:0718961395@192.168.0.12@192.168.0.12;user=phone> Call-ID: 739682a1@pbx CSeq: 22373 INVITE Max-Forwards: 70 Contact: <sip:play@192.168.0.12:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snomONE/2011-4.5.0.1050 Coma Berenicids P-Asserted-Identity: "ECN" <sip:play@192.168.0.19> P-Charging-Vector: icid-value=;icid-generated-at=192.168.0.12;orig-ioi=192.168.0.12 Content-Type: application/sdp Content-Length: 384 v=0 o=- 1384158937 1384158937 IN IP4 192.168.0.12 s=- c=IN IP4 192.168.0.12 t=0 0 m=audio 28552 RTP/AVP 18 0 8 9 2 3 101 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2012/06/06 11:56:21: SIP Rx udp:192.168.0.19:5060: SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 192.168.0.12:5060;branch=z9hG4bK-23ddcf1f2f619a06a96c113862f8dc5b;rport From: <sip:8025@192.168.0.12;user=phone>;tag=687137098 To: <sip:0718961395@192.168.0.12@192.168.0.12;user=phone> Call-ID: 739682a1@pbx CSeq: 22373 INVITE Server: Patton SN4960 4E30VRD 00A0BA073946 R5.7 2011-05-13 H323 RBS SIP M5T SIP Stack/4.0.30.30 Content-Type: text/plain Content-Length: 21 Invalid header(s): To ************************************************************ The CSTA Soap conversation: POST / HTTP/1.1 Content-Type: application/xml Host: 192.168.0.12 Content-Length: 337 Expect: 100-continue Connection: Keep-Alive <?xml version="1.0" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx"><env:Body><sns:MakeCall><domain></domain><callingDevice>8025@192.168.0.12</callingDevice><calledDirectoryNumber>0718961395</calledDirectoryNumber></sns:MakeCall></env:Body></env:Envelope> HTTP/1.1 200 Ok Content-Type: application/xml Content-Length: 418 <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><SOAP-ENV:Body><csta:MakeCallResponse><csta:callingDevice><csta:callID>7f9bfbe1@pbx</csta:callID><csta:deviceID>8025@192.168.0.12</csta:deviceID></csta:callingDevice></csta:MakeCallResponse></SOAP-ENV:Body></SOAP-ENV:Envelope> Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.