<div dir="ltr">Ok this is finally resolved, with the kind help of Daniel and Lorenzo. For future reference, below the problem. The solution was to change <div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">modparam("uac","restore_mode",</span><span style="font-family:arial,sans-serif;font-size:13px">"auto") to </span><span style="font-family:arial,sans-serif;font-size:13px">modparam("uac","restore_mode",</span><span style="font-family:arial,sans-serif;font-size:13px">"none")</span><br style="font-family:arial,sans-serif;font-size:13px">
<div><br></div><div style>I am not entirely sure if there are any adverse effects to doing this. If anybody can think of any, please let us know. I have not picked up any problems after changing this.</div><div style><br>
</div><div style><br></div><div style>The reason for changing it was:</div><div><br></div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">The problem is the following, and it's related to the kamailio UAC module.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">This module works like this:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">"It adds an alternative implementation to the AUTO mode for</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">uac_replace_from/to() by using the dialog module to store the URIs.</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">Here is the excerpt from the README file explaining this:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> If you set restore_mode to AUTO, the URI will be modified automatically</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> in all subsequent requests and replies in that dialog.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> There are two ways in which the AUTO mode can be achieved.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">1) One uses the rr module and appends to the Record-Route header a</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> parameter containing some strings from which the original and new</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">URI can be computed. The problem with this mode is that it relies on the</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> fact the parties will send the Route exactly as it was received. In</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> case there is a change, the resulting URIs will not be correct.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">2) The other one uses the dialog module to store the original and new</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">URI.</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> If you already use dialog module in your configuration, this is the</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> advisable mode. All you need to do to use this is to call dlg_manage()</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> before calling uac_replace_to(). It works by storing the URIs as dialog</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"> variables and registering callbacks in dialog module for in dialog</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px"> requests."</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">In our case, NGCP use the FIRST one, so we stored a string in the RR</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">header in order to restore the original From for the sebsequent request</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">(RE-INVITE).</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">Which parameter we use is set in the following line:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">modparam("uac", "rr_from_store_param", "vsf")</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">And if you look at a capture of a call, you can see the paramenter in</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">the 200 OK from NGCP to the caller:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px"><sip:127.0.0.1:5062;lr=on;</span><span style="font-family:arial,sans-serif;font-size:13px">ftag=</span><span style="font-family:arial,sans-serif;font-size:13px">KmsqOjkyLjI0MC4wLjEyOjUwODM;</span><span style="font-family:arial,sans-serif;font-size:13px">did=2ec.3bc;mpd=ii;ice_caller=</span><span style="font-family:arial,sans-serif;font-size:13px">strip;ice_callee=strip;rtpprx=</span><span style="font-family:arial,sans-serif;font-size:13px">yes;vsf=</span><span style="font-family:arial,sans-serif;font-size:13px">V3V3Z0VMeGFUOU1OZkthYTonJjQKay</span><span style="font-family:arial,sans-serif;font-size:13px">ohWlMrByZQLi8IKhkEHQdJAThbDQY-</span><span style="font-family:arial,sans-serif;font-size:13px">></span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">Now, the problem seems that your caller sent a Re-INVITE with a</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">truncated Route header, so NGCP was not able to look up properly the</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">original From.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">From UAC module:</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">"The problem with this mode is that it relies on the fact the parties</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">will send the Route exactly as it was received. In case there is a</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">change, the resulting URIs will not be correct."</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">I think this it the problem in your case.</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">See also:</span><br style="font-family:arial,sans-serif;font-size:13px"><a href="http://lists.sip-router.org/pipermail/sr-users/2012-July/073837.html" target="_blank" style="font-family:arial,sans-serif;font-size:13px">http://lists.sip-router.org/pipermail/sr-users/2012-July/073837.html</a><br>
</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 11:00 AM, Daniel Grotti <span dir="ltr"><<a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Theo,<br>
<br>
do you have another pcap to send to us ?<br>
<br>
Daniel<br>
<div class="im"><br>
<br>
<br>
On 09/17/2013 11:07 PM, Theo wrote:<br>
> Hi<br>
><br>
> Those headers are now gone and it would appear the size is comfortably<br>
> below 1500 now.<br>
><br>
><br>
> On Tue, Sep 17, 2013 at 9:22 PM, Lorenzo Mangani<br>
</div><div class="im">> <<a href="mailto:lorenzo.mangani@gmail.com">lorenzo.mangani@gmail.com</a> <mailto:<a href="mailto:lorenzo.mangani@gmail.com">lorenzo.mangani@gmail.com</a>>> wrote:<br>
><br>
> Hi Theo,<br>
><br>
> Do the packets still reach the peer with the extra headers or were<br>
> they removed as intended?<br>
><br>
><br>
> Best,<br>
><br>
> Lorenzo Mangani<br>
><br>
> HOMER DEV TEAM<br>
> QXIP - Capture Engineering<br>
><br>
><br>
><br>
> On Tue, Sep 17, 2013 at 9:11 PM, Theo <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> Hi<br>
><br>
> CSI has nothing on us! I have corrected the sems config - the<br>
> whitelist is back. Applied. I still have the same problem though...<br>
><br>
> Any more thoughts?<br>
><br>
><br>
> On Tue, Sep 17, 2013 at 3:49 PM, Lorenzo Mangani<br>
</div>> <<a href="mailto:lorenzo.mangani@gmail.com">lorenzo.mangani@gmail.com</a> <mailto:<a href="mailto:lorenzo.mangani@gmail.com">lorenzo.mangani@gmail.com</a>>><br>
<div><div class="h5">> wrote:<br>
><br>
> All,<br>
><br>
> A little update on this interesting rabbit-hole case - the<br>
> following was the result of a CSI:Style intercontinental<br>
> investigation with the help of Daniel Grotti from sip:wise.<br>
><br>
> The issue Theo was experiencing was surely caused by MTU<br>
> fragmentation. The MTU fragmentation was caused by the<br>
> messages being oversize, but the messages were really<br>
> oversize because still carrying a few SPCE internal headers,<br>
> not removed due to a previous customization of the sems<br>
> config in fact disabling is header filtering completely -<br>
> just to allow Refer messages to pass.<br>
> Quite a backlog story for this case! Now the solution to<br>
> both old and new issues here is clearly to correct SEMS<br>
> crippled configuration by defining a "header_filter" mode<br>
> (whitelist) and extending the "header_list" parameter list<br>
> with the whole Refer family of headers (or whatever else<br>
> needed within reason) and let the B2BUA remove all the<br>
> remaining internal-only headers from the peering sessions.<br>
> This should bring the situation back to normal as of packet<br>
> size without impacting any additional functionality.<br>
><br>
> Theo, let us know if this resolved your case,<br>
><br>
> Best,<br>
><br>
> Lorenzo Mangani<br>
><br>
> HOMER DEV TEAM<br>
> QXIP - Capture Engineering<br>
><br>
><br>
><br>
> On Tue, Sep 17, 2013 at 8:13 AM, Theo<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div></div><div><div class="h5">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> Hi<br>
><br>
> I have no solution for my problem. Part of this is kept<br>
> in private with Andreas because of the info in the log<br>
> files. The issue is bizarre as far as I can judge this.<br>
> We have 3 providers. In this case each of those transit<br>
> calls from a number of carriers which go through to this<br>
> one customer. All works fine. EXCEPT for the transit<br>
> from carrier 1, through provider A, who also transit for<br>
> other carriers, through the same trunk without issues.<br>
> The same carrier also sends calls through another<br>
> provider without issues. However, calls from carrier 1<br>
> through provider A cut after 5 seconds, about 80% of the<br>
> time.<br>
><br>
> ngrep-sip complains about "SIP/2.0 400 missing CSeq<br>
> header field'" - but The carrier, nor the provider, nor<br>
> me see anything missing. Ngrep-sip from the point of the<br>
> invite. I have decided not to worry about the sensitive<br>
> details at this point as I have to get this resolved<br>
> urgently. I see nothing missing in the invite. What I do<br>
> see is, the second last line, that doesn't make sense.<br>
> That should be a full domain, but where does that come<br>
> from???<br>
><br>
> Is this an issue on our box? if so, why only with this<br>
> particular upstream carrier through this particular<br>
> provider. If not, how do I get the other party to fix it?<br>
><br>
> Thanks for any input<br>
><br>
><br>
><br>
> U 2013/09/17 08:07:20.226723 <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
</div></div>> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>> -> <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>><br>
> INVITE sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a> <<a href="http://127.0.0.1:5080" target="_blank">http://127.0.0.1:5080</a>> SIP/2.0'<br>
<div class="im">> Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">> Record-Route:<br>
> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">> Route:<br>
> <sip:ngcp-lb@127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;did=3f2.531;mpd=ii;ice_caller=strip;ice_callee=strip;rtpprx=yes;vsf=V3V3Z0VMeGFUOU1OZkthYTonJjQKayohWlMrByZQLi8IKhkEHQdJAThbDQY->'<br>
> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bK7239.6843b44cb370e058f995c996d166891a.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bK7239.908cd0b7.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.12:5083;branch=z9hG4bK685c.a3419e67.0'<br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODM'<br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=62DF6E4A-5237F1970000DBD6-69F4A700'<br>
<div class="im">> Call-ID:<br>
> hs4_bhs6_bSDg3ivb01-4893e0c5872c548cdb6488e80b76e5db-ctvvfv3'<br>
> CSeq: 2 INVITE'<br>
> Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay'<br>
> Contact: <sip:27214482133@92.240.0.12:5083;transport=udp>'<br>
> MIME-Version: 1.0'<br>
> Supported: timer,100rel'<br>
> Max-Forwards: 63'<br>
> Session-Expires: 1800;refresher=uac'<br>
> Allow: ACK, INFO, BYE, CANCEL, INVITE, OPTIONS, NOTIFY,<br>
> PRACK, UPDATE'<br>
> Content-Type: application/sdp'<br>
> Content-Length: 234'<br>
> P-NGCP-Src-Ip: 92.240.1.12'<br>
> P-NGCP-Src-Port: 5060'<br>
> P-NGCP-Src-Proto: udp'<br>
> P-NGCP-Src-Af: 4'<br>
> P-Sock-Info: udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>'<br>
<div class="im">> '<br>
> v=0'<br>
> o=- 2445083187 307757073 IN IP4 92.240.0.61'<br>
> s=-'<br>
> c=IN IP4 92.240.0.61'<br>
> t=0 0'<br>
> m=audio 52438 RTP/AVP 18 101'<br>
> a=rtpmap:18 G729/8000'<br>
> a=fmtp:18 annexb=no'<br>
> a=rtpmap:101 telephone-event/8000'<br>
> a=fmtp:101 0-15'<br>
> a=sendrecv'<br>
> a=ptime:60'<br>
><br>
> #<br>
> U 2013/09/17 08:07:20.226832 <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
</div>> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>> -> <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>><br>
<div class="im">> SIP/2.0 100 Trying'<br>
> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bK7239.6843b44cb370e058f995c996d166891a.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bK7239.908cd0b7.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.12:5083;branch=z9hG4bK685c.a3419e67.0'<br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODM'<br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=62DF6E4A-5237F1970000DBD6-69F4A700'<br>
<div class="im">> Call-ID:<br>
> hs4_bhs6_bSDg3ivb01-4893e0c5872c548cdb6488e80b76e5db-ctvvfv3'<br>
> CSeq: 2 INVITE'<br>
> P-Out-Socket: udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>'<br>
<div class="im">> Server: Sipwise NGCP Proxy 2.X'<br>
> Content-Length: 0'<br>
> '<br>
><br>
> #<br>
> U 2013/09/17 08:07:20.227036 <a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>> -> <a href="http://92.240.1.12:5060" target="_blank">92.240.1.12:5060</a><br>
> <<a href="http://92.240.1.12:5060" target="_blank">http://92.240.1.12:5060</a>><br>
<div class="im">> SIP/2.0 100 Trying'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bK7239.908cd0b7.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.12:5083;branch=z9hG4bK685c.a3419e67.0'<br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODM'<br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=62DF6E4A-5237F1970000DBD6-69F4A700'<br>
<div class="im">> Call-ID:<br>
> hs4_bhs6_bSDg3ivb01-4893e0c5872c548cdb6488e80b76e5db-ctvvfv3'<br>
> CSeq: 2 INVITE'<br>
> Server: Sipwise NGCP Proxy 2.X'<br>
> Content-Length: 0'<br>
> '<br>
><br>
> #<br>
> U 2013/09/17 08:07:20.227510 <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
</div>> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>> -> <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>><br>
<div class="im">> SIP/2.0 400 missing CSeq header field'<br>
> Record-Route:<br>
> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>'<br>
> Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">> Record-Route:<br>
> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODM;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bK7239.6843b44cb370e058f995c996d166891a.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bK7239.908cd0b7.0'<br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.12:5083;branch=z9hG4bK685c.a3419e67.0'<br>
> From: <sip:27214482133@maodi.sw1.a]''''S'''<br>
> Content-Length: 0'<br>
> '<br>
><br>
><br>
><br>
><br>
><br>
> On Fri, Sep 13, 2013 at 4:28 PM, Theo<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> I starting to think this is a problem on my box.<br>
> However, it ONLY does it with this client and ONLY<br>
> from one upstream provider who route calls to us<br>
> from various carriers. It only happens with calls<br>
> from one carrier. From the sems log I have made the<br>
> line below in BOLD. that should read<br>
> @<a href="http://maodi.sw1.africanaxess.co.za" target="_blank">maodi.sw1.africanaxess.co.za</a><br>
</div>> <<a href="http://maodi.sw1.africanaxess.co.za" target="_blank">http://maodi.sw1.africanaxess.co.za</a>>. It does on<br>
<div class="im">> the first invite. Where does this change into the<br>
> mangled part??? And why only on calls through one<br>
> provider from one carrier specifically.<br>
><br>
><br>
><br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [parse_sip_uri, parse_uri.cpp:332] DEBUG: Converted<br>
> URI port (5080) to int (5080)<br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [parse_headers, parse_header.cpp:391] DEBUG: Illegal<br>
> CR or LF in header name<br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [received_msg, trans_layer.cpp:1093] DEBUG:<br>
> parse_sip_msg returned -5<br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [received_msg, trans_layer.cpp:1099] DEBUG: parsing<br>
> error: missing CSeq header field<br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [received_msg, trans_layer.cpp:1101] DEBUG: Message<br>
> was: "INVITE sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a><br>
</div>> <<a href="http://127.0.0.1:5080" target="_blank">http://127.0.0.1:5080</a>> SIP/2.0#015#012Record-Route:<br>
<div class="im">> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>#015#012Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Record-Route:<br>
<div class="im">> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Via:<br>
<div class="im">> SIP/2.0/UDP<br>
> 127.0.0.1:5062;branch=z9hG4bKdf2f.16949b1e10816e7aeabf87354bed5bba.0#015#012Via:<br>
> SIP/2.0/UDP<br>
</div>> 127.0.0.1;branch=z9hG4bKdf2f.7bc23c3315f2e5d9705a33335a27931e.0#015#012*Via:<br>
<div class="im">> SIP/2.0/UDP<br>
> 92.240.1.13;rport=5060;branch=z9hG4bKdf2f.584bf716.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.0.12:5081;branch=z9hG4bKbb6b.792a931.0#015#012From:<br>
> <sip:27214482133@maodi.sw1.a]#007#032#006#023S#021#020#012#035#<a href="http://026.co.za" target="_blank">026.co.za</a><br>
</div>> <<a href="http://026.co.za" target="_blank">http://026.co.za</a>>*>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODE#015#012To:<br>
> <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=580524BE-52331AAE00079EFB-69F4A700#015#012Call-ID:<br>
<div><div class="h5">> hs4_bhs6_bSDdbf7b01-fb9203bf7ff514193081e8be537bc659-ctvvfv3#015#012CSeq:<br>
> 2 INVITE#015#012Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay#015#012Contact:<br>
> <sip:27214482133@92.240.0.12:5081;transport=udp>#015#012MIME-Version:<br>
> 1.0#015#012Supported:<br>
> timer,100rel#015#012Max-Forwards:<br>
> 62#015#012Session-Expires:<br>
> 1800;refresher=uac#015#012Allow: ACK, INFO, BYE,<br>
> CANCEL, INVITE, OPTIONS, NOTIFY, PRACK,<br>
> UPDATE#015#012Content-Type:<br>
> application/sdp#015#012Content-Length:<br>
> 254#015#012#015#012v=0#015#012o=- 4048552998<br>
> 309592175 IN IP4<br>
> 196.41.123.113#015#012s=-#015#012c=IN IP4<br>
> 196.41.123.113#015#012t=0 0#015#012m=audio 31636<br>
> RTP/AVP 18 101#015#012a=rtpmap:18<br>
> G729/8000#015#012a=fmtp:18<br>
> annexb=no#015#012a=rtpmap:101<br>
> telephone-event/8000#015#012a=fmtp:101<br>
> 0-15#015#012a=sendrecv#015#012a=ptime:60#015#012a=rtcp:31637#015#012"<br>
> Sep 13 16:01:18 sipwise sems[2424]: [#7ffb69f4a700]<br>
> [send, transport.cpp:98] DEBUG: send<br>
> msg#012--++--#012SIP/2.0 400 missing CSeq header<br>
> field#015#012Record-Route:<br>
> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>#015#012Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div></div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Record-Route:<br>
<div class="im">> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Via:<br>
<div class="im">> SIP/2.0/UDP<br>
> 127.0.0.1:5062;branch=z9hG4bKdf2f.16949b1e10816e7aeabf87354bed5bba.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKdf2f.7bc23c3315f2e5d9705a33335a27931e.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.1.13;rport=5060;branch=z9hG4bKdf2f.584bf716.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.0.12:5081;branch=z9hG4bKbb6b.792a931.0#015#012From:<br>
> <sip:27214482133@maodi.sw1.a]#007#032#006#023S#021#020#015#012Content-Length:<br>
> 0#015#012#015#012--++--<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [run, udp_trsp.cpp:213] DEBUG: vv M [|] u recvd msg<br>
> via UDP vv#012--++--#012INVITE sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a><br>
</div>> <<a href="http://127.0.0.1:5080" target="_blank">http://127.0.0.1:5080</a>> SIP/2.0#015#012Record-Route:<br>
<div class="im">> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>#015#012Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Record-Route:<br>
<div class="im">> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Via:<br>
<div class="im">> SIP/2.0/UDP<br>
> 127.0.0.1:5062;branch=z9hG4bKdf2f.16949b1e10816e7aeabf87354bed5bba.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKdf2f.7bc23c3315f2e5d9705a33335a27931e.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.1.13;rport=5060;branch=z9hG4bKdf2f.584bf716.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.0.12:5081;branch=z9hG4bKbb6b.792a931.0#015#012From:<br>
> <sip:27214482133@maodi.sw1.a]#007#032#006#023S#021#020#012#035#<a href="http://026.co.za" target="_blank">026.co.za</a><br>
</div>> <<a href="http://026.co.za" target="_blank">http://026.co.za</a>>>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODE#015#012To:<br>
> <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=580524BE-52331AAE00079EFB-69F4A700#015#012Call-ID:<br>
<div><div class="h5">> hs4_bhs6_bSDdbf7b01-fb9203bf7ff514193081e8be537bc659-ctvvfv3#015#012CSeq:<br>
> 2 INVITE#015#012Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay#015#012Contact:<br>
> <sip:27214482133@92.240.0.12:5081;transport=udp>#015#012MIME-Version:<br>
> 1.0#015#012Supported:<br>
> timer,100rel#015#012Max-Forwards:<br>
> 62#015#012Session-Expires:<br>
> 1800;refresher=uac#015#012Allow: ACK, INFO, BYE,<br>
> CANCEL, INVITE, OPTIONS, NOTIFY, PRACK,<br>
> UPDATE#015#012Content-Type:<br>
> application/sdp#015#012Content-Length:<br>
> 254#015#012#015#012v=0#015#012o=- 4048552998<br>
> 309592175 IN IP4<br>
> 196.41.123.113#015#012s=-#015#012c=IN IP4<br>
> 196.41.123.113#015#012t=0 0#015#012m=audio 31636<br>
> RTP/AVP 18 101#015#012a=rtpmap:18<br>
> G729/8000#015#012a=fmtp:18<br>
> annexb=no#015#012a=rtpmap:101<br>
> telephone-event/8000#015#012a=fmtp:101<br>
> 0-15#015#012a=sendrecv#015#012a=ptime:60#015#012a=rtcp:31637#015#012--++--<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [parse_sip_uri, parse_uri.cpp:332] DEBUG: Converted<br>
> URI port (5080) to int (5080)<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [parse_headers, parse_header.cpp:391] DEBUG: Illegal<br>
> CR or LF in header name<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [received_msg, trans_layer.cpp:1093] DEBUG:<br>
> parse_sip_msg returned -5<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [received_msg, trans_layer.cpp:1099] DEBUG: parsing<br>
> error: missing CSeq header field<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [received_msg, trans_layer.cpp:1101] DEBUG: Message<br>
> was: "INVITE sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a><br>
</div></div>> <<a href="http://127.0.0.1:5080" target="_blank">http://127.0.0.1:5080</a>> SIP/2.0#015#012Record-Route:<br>
<div class="im">> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>#015#012Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Record-Route:<br>
<div class="im">> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEyOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>#015#012Via:<br>
<div class="im">> SIP/2.0/UDP<br>
> 127.0.0.1:5062;branch=z9hG4bKdf2f.16949b1e10816e7aeabf87354bed5bba.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKdf2f.7bc23c3315f2e5d9705a33335a27931e.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.1.13;rport=5060;branch=z9hG4bKdf2f.584bf716.0#015#012Via:<br>
> SIP/2.0/UDP<br>
> 92.240.0.12:5081;branch=z9hG4bKbb6b.792a931.0#015#012From:<br>
> <sip:27214482133@maodi.sw1.a]#007#032#006#023S#021#020#012#035#<a href="http://026.co.za" target="_blank">026.co.za</a><br>
</div>> <<a href="http://026.co.za" target="_blank">http://026.co.za</a>>>;tag=KmsqOjkyLjI0MC4wLjEyOjUwODE#015#012To:<br>
> <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=580524BE-52331AAE00079EFB-69F4A700#015#012Call-ID:<br>
<div><div class="h5">> hs4_bhs6_bSDdbf7b01-fb9203bf7ff514193081e8be537bc659-ctvvfv3#015#012CSeq:<br>
> 2 INVITE#015#012Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay#015#012Contact:<br>
> <sip:27214482133@92.240.0.12:5081;transport=udp>#015#012MIME-Version:<br>
> 1.0#015#012Supported:<br>
> timer,100rel#015#012Max-Forwards:<br>
> 62#015#012Session-Expires:<br>
> 1800;refresher=uac#015#012Allow: ACK, INFO, BYE,<br>
> CANCEL, INVITE, OPTIONS, NOTIFY, PRACK,<br>
> UPDATE#015#012Content-Type:<br>
> application/sdp#015#012Content-Length:<br>
> 254#015#012#015#012v=0#015#012o=- 4048552998<br>
> 309592175 IN IP4<br>
> 196.41.123.113#015#012s=-#015#012c=IN IP4<br>
> 196.41.123.113#015#012t=0 0#015#012m=audio 31636<br>
> RTP/AVP 18 101#015#012a=rtpmap:18<br>
> G729/8000#015#012a=fmtp:18<br>
> annexb=no#015#012a=rtpmap:101<br>
> telephone-event/8000#015#012a=fmtp:101<br>
> 0-15#015#012a=sendrecv#015#012a=ptime:60#015#012a=rtcp:31637#015#012"<br>
> Sep 13 16:01:19 sipwise sems[2424]: [#7ffb69e49700]<br>
> [send, transport.cpp:98] DEBUG: send<br>
> msg#012--++--#012SIP/2<br>
><br>
><br>
> On Fri, Sep 13, 2013 at 1:00 PM, Theo<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div></div><div class="im">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> Hi Andreas,<br>
><br>
> Apologies for keeping this off list - once I've<br>
> figured out the problem and if worth it for<br>
> other people I will post the correct solution<br>
> here. I have in the meantime figured out WHY the<br>
> call is dropping, and you were spot on with the<br>
> missing CSeq header field. This is a snippet of<br>
> a dropped call and clearly we are sending back<br>
> the SIP/2.0 400 missing CSeq header field'. What<br>
> I just cannot figure out is, WHAT is missing<br>
> exactly. The upstream guys are saying "nothing<br>
> is missing".<br>
><br>
> I do see From:<br>
> <sip:27214482133@maodi.sw1.a]''''S''' which is<br>
> worrying. this should be<br>
> <a href="http://maodi.sw1.africanaxess.co.za" target="_blank">maodi.sw1.africanaxess.co.za</a><br>
</div>> <<a href="http://maodi.sw1.africanaxess.co.za" target="_blank">http://maodi.sw1.africanaxess.co.za</a>> which is<br>
<div class="im">> the domain associated with this customer.<br>
><br>
> U 2013/09/13 11:58:07.520589 <a href="http://92.240.1.12:5060" target="_blank">92.240.1.12:5060</a><br>
</div>> <<a href="http://92.240.1.12:5060" target="_blank">http://92.240.1.12:5060</a>> -> <a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>><br>
><br>
> INVITE <a href="mailto:sip%3Angcp-lb@196.41.123.113">sip:ngcp-lb@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253Angcp-lb@196.41.123.113">sip%3Angcp-lb@196.41.123.113</a>>;ngcpct=c2lwOjEyNy4wLjAuMTo1MDgw<br>
> SIP/2.0'<br>
><br>
> Route: <<a href="mailto:sip%3Angcp-lb@196.41.123.113">sip:ngcp-lb@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253Angcp-lb@196.41.123.113">sip%3Angcp-lb@196.41.123.113</a>>;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>,<br>
> <<a href="mailto:sip%3Angcp-lb@127.0.0.1">sip:ngcp-lb@127.0.0.1</a><br>
> <mailto:<a href="mailto:sip%253Angcp-lb@127.0.0.1">sip%3Angcp-lb@127.0.0.1</a>>;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>,<br>
<div class="im">> <sip:ngcp-lb@127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;did=63b.e412;mpd=ii;ice_caller=strip;ice_callee=strip;rtpprx=yes;vsf=V3V3Z0VMeGFUOU1OZkthYTonJjQKayohWlMrByZQLi8IKhkEHQdJAThbDQY->'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;branch=z9hG4bKa6b5.0d018653.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.13:5081;branch=z9hG4bKf784.ce567e76.0'<br>
><br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEzOjUwODE'<br>
><br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=3D4A701D-5232E1AF0004AA9D-69F4A700'<br>
<div class="im">><br>
> Call-ID:<br>
> hs4_bhs6_bSDtqpbc01-50b38cb585afe88c67431dd52af8b9dd-ctvvfv3'<br>
><br>
> CSeq: 2 INVITE'<br>
><br>
> Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay'<br>
><br>
> Contact:<br>
> <sip:27214482133@92.240.0.13:5081;transport=udp>'<br>
><br>
> MIME-Version: 1.0'<br>
><br>
> Supported: timer,100rel'<br>
><br>
> Max-Forwards: 64'<br>
><br>
> Session-Expires: 1800;refresher=uac'<br>
><br>
> Allow: ACK, INFO, BYE, CANCEL, INVITE, OPTIONS,<br>
> NOTIFY, PRACK, UPDATE'<br>
><br>
> Content-Type: application/sdp'<br>
><br>
> Content-Length: 235'<br>
><br>
> '<br>
><br>
> v=0'<br>
><br>
</div>> o=- <a href="tel:3522956930" value="+13522956930">3522956930</a> <tel:<a href="tel:3522956930" value="+13522956930">3522956930</a>> 307888210 IN IP4<br>
<div class="im">> 92.240.0.62'<br>
><br>
> s=-'<br>
><br>
> c=IN IP4 92.240.0.62'<br>
><br>
> t=0 0'<br>
><br>
> m=audio 51314 RTP/AVP 18 101'<br>
><br>
> a=rtpmap:18 G729/8000'<br>
><br>
> a=fmtp:18 ann<br>
><br>
> #<br>
><br>
> U 2013/09/13 11:58:07.520787 <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
</div>> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>> -> <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>><br>
><br>
> INVITE sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a><br>
> <<a href="http://127.0.0.1:5080" target="_blank">http://127.0.0.1:5080</a>> SIP/2.0'<br>
<div class="im">><br>
> Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">><br>
> Record-Route:<br>
> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">><br>
> Route:<br>
> <sip:ngcp-lb@127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;did=63b.e412;mpd=ii;ice_caller=strip;ice_callee=strip;rtpprx=yes;vsf=V3V3Z0VMeGFUOU1OZkthYTonJjQKayohWlMrByZQLi8IKhkEHQdJAThbDQY->'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKa6b5.242fbc2bf219d6f43d00babcdc3c29f3.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bKa6b5.0d018653.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.13:5081;branch=z9hG4bKf784.ce567e76.0'<br>
><br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEzOjUwODE'<br>
><br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=3D4A701D-5232E1AF0004AA9D-69F4A700'<br>
<div class="im">><br>
> Call-ID:<br>
> hs4_bhs6_bSDtqpbc01-50b38cb585afe88c67431dd52af8b9dd-ctvvfv3'<br>
><br>
> CSeq: 2 INVITE'<br>
><br>
> Accept:<br>
> application/sdp,application/isup,multipart/mixed,application/vnd.siemens.key-event,application/vnd.siemens.surpass,application/dtmf-relay'<br>
><br>
> Contact:<br>
> <sip:27214482133@92.240.0.13:5081;transport=udp>'<br>
><br>
> MIME-Version: 1.0'<br>
><br>
> Supported: timer,100rel'<br>
><br>
> Max-Forwards: 63'<br>
><br>
> Session-Expires: 1800;refresher=uac'<br>
><br>
> Allow: ACK, INFO, BYE, CANCEL, INVITE, OPTIONS,<br>
> NOTIFY, PRACK, UPDATE'<br>
><br>
> Content-Type: application/sdp'<br>
><br>
> Content-Length: 235'<br>
><br>
> P-NGCP-Src-Ip: 92.240.1.12'<br>
><br>
> P-NGCP-Src-Port: 5060'<br>
><br>
> P-NGCP-Src-Proto: udp'<br>
><br>
> P-NGCP-Src-Af: 4'<br>
><br>
> P-Sock-Info: udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>'<br>
><br>
> '<br>
><br>
> v=0'<br>
><br>
> o=- <a href="tel:3522956930" value="+13522956930">3522956930</a> <tel:<a href="tel:3522956930" value="+13522956930">3522956930</a>> 307888210 IN IP4<br>
<div class="im">> 92.240.0.62'<br>
><br>
> s=-'<br>
><br>
> c=IN IP4 92.240.0.62'<br>
><br>
> t=0 0'<br>
><br>
> m=audio 51314 RTP/AVP 18 101'<br>
><br>
> a=rtpmap:18 G729/8000'<br>
><br>
> a=fmtp:18 annexb=no'<br>
><br>
> a=rtpmap:101 telephone-event/8000'<br>
><br>
> a=fmtp:101 0-15'<br>
><br>
> a=sendrecv'<br>
><br>
> a=pmft: T38'<br>
><br>
><br>
> #<br>
><br>
> U 2013/09/13 11:58:07.520906 <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
</div>> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>> -> <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>><br>
<div class="im">><br>
> SIP/2.0 100 Trying'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKa6b5.242fbc2bf219d6f43d00babcdc3c29f3.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bKa6b5.0d018653.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.13:5081;branch=z9hG4bKf784.ce567e76.0'<br>
><br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEzOjUwODE'<br>
><br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=3D4A701D-5232E1AF0004AA9D-69F4A700'<br>
<div class="im">><br>
> Call-ID:<br>
> hs4_bhs6_bSDtqpbc01-50b38cb585afe88c67431dd52af8b9dd-ctvvfv3'<br>
><br>
> CSeq: 2 INVITE'<br>
><br>
> P-Out-Socket: udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>'<br>
<div class="im">><br>
> Server: Sipwise NGCP Proxy 2.X'<br>
><br>
> Content-Length: 0'<br>
><br>
> '<br>
><br>
><br>
> #<br>
><br>
> U 2013/09/13 11:58:07.521217 <a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>> -> <a href="http://92.240.1.12:5060" target="_blank">92.240.1.12:5060</a><br>
> <<a href="http://92.240.1.12:5060" target="_blank">http://92.240.1.12:5060</a>><br>
><br>
<div class="im">> SIP/2.0 100 Trying'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bKa6b5.0d018653.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.13:5081;branch=z9hG4bKf784.ce567e76.0'<br>
><br>
> From: <<a href="mailto:sip%3A27214482133@92.240.1.12">sip:27214482133@92.240.1.12</a><br>
</div>> <mailto:<a href="mailto:sip%253A27214482133@92.240.1.12">sip%3A27214482133@92.240.1.12</a>>;user=phone>;tag=KmsqOjkyLjI0MC4wLjEzOjUwODE'<br>
><br>
> To: <<a href="mailto:sip%3A27110254990@196.41.123.113">sip:27110254990@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253A27110254990@196.41.123.113">sip%3A27110254990@196.41.123.113</a>>;user=phone>;tag=3D4A701D-5232E1AF0004AA9D-69F4A700'<br>
<div class="im">><br>
> Call-ID:<br>
> hs4_bhs6_bSDtqpbc01-50b38cb585afe88c67431dd52af8b9dd-ctvvfv3'<br>
><br>
> CSeq: 2 INVITE'<br>
><br>
> Server: Sipwise NGCP Proxy 2.X'<br>
><br>
> Content-Length: 0'<br>
><br>
> '<br>
><br>
><br>
> #<br>
><br>
> U 2013/09/13 11:58:07.521712 <a href="http://127.0.0.1:5062" target="_blank">127.0.0.1:5062</a><br>
</div>> <<a href="http://127.0.0.1:5062" target="_blank">http://127.0.0.1:5062</a>> -> <a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a><br>
> <<a href="http://127.0.0.1:5060" target="_blank">http://127.0.0.1:5060</a>><br>
<div class="im">><br>
> SIP/2.0 400 missing CSeq header field'<br>
><br>
> Record-Route:<br>
> <sip:127.0.0.1:5062;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;rtpprx=yes;ice_callee=strip;ice_caller=strip;mpd=ii>'<br>
><br>
> Record-Route:<br>
> <sip:127.0.0.1;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">><br>
> Record-Route:<br>
> <sip:196.41.123.113;r2=on;lr=on;ftag=KmsqOjkyLjI0MC4wLjEzOjUwODE;ngcplb=yes;socket=udp:<a href="http://196.41.123.113:5060" target="_blank">196.41.123.113:5060</a><br>
</div>> <<a href="http://196.41.123.113:5060" target="_blank">http://196.41.123.113:5060</a>>>'<br>
<div class="im">><br>
> Via: SIP/2.0/UDP<br>
> 127.0.0.1;branch=z9hG4bKa6b5.242fbc2bf219d6f43d00babcdc3c29f3.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.1.12;rport=5060;branch=z9hG4bKa6b5.0d018653.0'<br>
><br>
> Via: SIP/2.0/UDP<br>
> 92.240.0.13:5081;branch=z9hG4bKf784.ce567e76.0'<br>
><br>
> From: <sip:27214482133@maodi.sw1.a]''''S'''<br>
><br>
> Content-Length: 0'<br>
><br>
> '<br>
><br>
><br>
><br>
> On Tue, Sep 10, 2013 at 2:43 PM, Theo<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> Hi<br>
><br>
> Any idea why the tcpdump get mangled when<br>
> saving to a file?<br>
><br>
> ?E???#@??){q)?3???i?SIP/2.0 200 OK<br>
><br>
> for example? when watching it in real-time<br>
> it looks fine<br>
><br>
><br>
> On Tue, Sep 10, 2013 at 1:33 PM, Theo<br>
> <<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:axessofficetheo@gmail.com">axessofficetheo@gmail.com</a>>> wrote:<br>
><br>
> Hi<br>
><br>
> Homer is on my list of things :-)<br>
> Lorenzo has been telling how great it is.<br>
><br>
> I didn't see that in the log, but mainly<br>
> because of ignorance. For example, I<br>
> have no idea what a CSeq header field<br>
> is, but straight after this mail i will<br>
> consult my friend google on that one. I<br>
> will run the tcpdump and wait for more<br>
> examples.<br>
><br>
> And speed up my homer box I guess.<br>
><br>
><br>
> On Tue, Sep 10, 2013 at 1:03 PM, Andreas<br>
> Granig <<a href="mailto:agranig@sipwise.com">agranig@sipwise.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:agranig@sipwise.com">agranig@sipwise.com</a>>> wrote:<br>
><br>
> Hi,<br>
><br>
> Did you recognize the "SIP/2.0 400<br>
> missing CSeq header field" in the<br>
> sems log? Seems like there is quite<br>
> a lot broken with the clients<br>
> involved here.<br>
><br>
> I think the only way to pin it down<br>
> exactly is to do something like<br>
><br>
> tcpdump -i any -s 0 -w<br>
> /path/to/trace.pcap host xxx.xxx.xxx.xxx<br>
><br>
> where xxx.xxx.xxx.xxx is this<br>
> asterisk box to get a clear overview<br>
> of what's going on. Another (better)<br>
> way to troubleshoot this stuff post<br>
> mortem is to install Homer, so<br>
> you're able to analyze call flows<br>
> which happened in the past.<br>
><br>
> Andreas<br>
><br>
><br>
> On 09/10/2013 12:54 PM, Andreas<br>
> Granig wrote:<br>
><br>
> Hi,<br>
><br>
> On 09/10/2013 12:42 PM, Theo wrote:<br>
><br>
> Sep 10 11:16:06 sipwise<br>
> /usr/sbin/kamailio[1971]:<br>
> INFO: <script>: New<br>
> request - M=BYE<br>
> R=<a href="mailto:sip%3Angcp-lb@196.41.123.113">sip:ngcp-lb@196.41.123.113</a><br>
> <mailto:<a href="mailto:sip%253Angcp-lb@196.41.123.113">sip%3Angcp-lb@196.41.123.113</a>><br>
</div></div>> <mailto:<a href="mailto:sip%253Angcp-lb@196.41.">sip%3Angcp-lb@196.41.</a>__123.113<br>
> <mailto:<a href="mailto:sip%25253Angcp-lb@196.41.123.113">sip%253Angcp-lb@196.41.123.113</a>>><br>
> F=<a href="mailto:sip%3A27219763939@92.240.1.12">sip:27219763939@92.240.1.12</a> <mailto:<a href="mailto:sip%253A27219763939@92.240.1.12">sip%3A27219763939@92.240.1.12</a>><br>
> <mailto:<a href="mailto:sip%253A27219763939@92.">sip%3A27219763939@92.</a>__240.1.12<br>
> <mailto:<a href="mailto:sip%25253A27219763939@92.240.1.12">sip%253A27219763939@92.240.1.12</a>>><br>
> T=<a href="mailto:sip%3A27214235154@196.41.123.">sip:27214235154@196.41.123.</a>__113<br>
> <mailto:<a href="mailto:sip%253A27214235154@196.41.123.113">sip%3A27214235154@196.41.123.113</a>><br>
> <mailto:<a href="mailto:sip%253A27214235154@196.">sip%3A27214235154@196.</a>__41.123.113<br>
> <mailto:<a href="mailto:sip%25253A27214235154@196.41.123.113">sip%253A27214235154@196.41.123.113</a>>><br>
<div class="im">> IP=udp:<a href="http://92.240.1.12:5060" target="_blank">92.240.1.12:5060</a><br>
> <<a href="http://92.240.1.12:5060" target="_blank">http://92.240.1.12:5060</a>><br>
</div>> <<a href="http://92.240.1.12:5060" target="_blank">http://92.240.1.12:5060</a>><br>
> ID=hs4_bhs6_bSDh3kvb01-__12c39d503671664b04bbf109d85784__78-ctvvfv3<br>
<div class="im">><br>
> In this case, which party<br>
> tore the call down?<br>
><br>
><br>
> In this case, the IP 92.240.1.12<br>
> sent the BYE (look for IP=xxxx)<br>
> in the<br>
> log line.<br>
><br>
> I think you're actually running<br>
> into an end-to-end media negotiation<br>
> issue. Caller sends SDP offer,<br>
> the callee sends the answer, and the<br>
> caller is not happy with it and<br>
> sends the BYE. Just a wild<br>
> guess, need<br>
> to check the logs in detail.<br>
><br>
> Andreas<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
</div>> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
> <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
> <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
<br>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
</div></div></blockquote></div><br></div>