<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Kamailio itself doesn't alter CSeq method, unless you do something
    in the configuration file.<br>
    <br>
    Looking at the traces, the broken CSeq comes like that to Kamailio
    -- first part here indicates that 192.168.0.1:5060
    is Kamailio, and next shows the packet sent by .0.33 to .0.1
    (kamailio):<br>
    <br>
    <pre wrap="">U 2015/06/22 17:08:52.730652 192.168.0.1:5060 -> 192.168.0.3:6060
SIP/2.0 100 trying -- your call is important to us</pre>
    ...<br>
    <pre wrap="">U 2015/06/22 17:08:52.735438 192.168.0.33:5060 -> 192.168.0.1:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK3504.df39a8277f82eb6121d9c32883c70ead.0;received=192.168.0.1;rport=5060
Via: SIP/2.0/UDP 192.168.0.3:6060;branch=z9hG4bK0a9b.47eca853.0
Max-Forwards: 70
To: <a class="moz-txt-link-rfc2396E" href="sip:1001@192.168.1.3:8000"><sip:1001@192.168.1.3:8000></a>;tag=krTfxNsCTuX
From: "PhonerLite" <a class="moz-txt-link-rfc2396E" href="sip:1000@192.168.1.3:8000"><sip:1000@192.168.1.3:8000></a>;tag=3066030555
Call-ID: SBCbFhRRnpBd3ZEUWNUVF8gQWVZREoKMXhvWVMSVCUxUzIVWSpCCUJ4cEdWZV1NQ0tFYQ
CSeq: 1
Contact: <a class="moz-txt-link-rfc2396E" href="sip:1001@192.168.0.33:5060"><sip:1001@192.168.0.33:5060></a>
Record-Route: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.1;lr=on"><sip:192.168.0.1;lr=on></a>
User-Agent: MAYAH 4.9.12.0-2.1.0.45
Content-Length: 0</pre>
    <br>
    So, if I got it right that .0.1 is kamailio, then the problem is not
    in kamailio at all.<br>
    <br>
    Cheers,<br>
    Daniel<br>
    <br>
    <div class="moz-cite-prefix">On 22/06/15 17:41, <a class="moz-txt-link-abbreviated" href="mailto:kai.ohnacker@cbc.de">kai.ohnacker@cbc.de</a>
      wrote:<br>
    </div>
    <blockquote
      cite="mid:5A4C35A70604964FBD46890CC952D954259F0C4F@MANA1.netrtlsrv.com"
      type="cite">
      <pre wrap="">In the txt file you can find the ngrep traffic.

Cheers, 
Kai

---------------------------------------------------------

Perhaps you have an ngrep of the sip traffic?

--fred

-----Ursprüngliche Nachricht-----
Von: sr-users [<a class="moz-txt-link-freetext" href="mailto:sr-users-bounces@lists.sip-router.org">mailto:sr-users-bounces@lists.sip-router.org</a>] Im Auftrag von Fred Posner
Gesendet: Montag, 22. Juni 2015 16:39
An: <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
Betreff: Re: [SR-Users] Kamailio with Blox SBC (opensips based) - Wrong CSeq


On 06/22/2015 10:30 AM, <a class="moz-txt-link-abbreviated" href="mailto:kai.ohnacker@cbc.de">kai.ohnacker@cbc.de</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hello,

my setup is a kamailio server as registrar and Blox as SBC.

Blox is a freeware GUI with Opensips as framework.

Kamailio is located in the private network and Blox operates with 2 NICs
(private and public)

Now the following problem:

If I make a call from public (phonerlite) to private (mayah), the
connection don't reach the "framed" state and is "broken" after 30 sec.

After evaluating the log files, I found that the CSeq from Kamailio is
wrong.

The invite comes from

CSeq: 9 INVITE

The reply is with CSeq 1

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.3:6060;branch=z9hG4bK38ae.cf317344.0
Max-Forwards: 70
To: <a class="moz-txt-link-rfc2396E" href="sip:1001@192.168.1.3:8000"><sip:1001@192.168.1.3:8000></a>;tag=qTKGZvr0ItW
From: "PhonerLite" <a class="moz-txt-link-rfc2396E" href="sip:1000@192.168.1.3:8000"><sip:1000@192.168.1.3:8000></a>;tag=1005520878
Call-ID:
SBCbFgsQn5HcHpEUxJUVF8gQWVZREt6QwJvWVJkXCdAUzdkXl41CUJ4cEdWZV1NQ0tFYQ
CSeq: 1
Contact: <a class="moz-txt-link-rfc2396E" href="sip:1001@192.168.0.33:5060"><sip:1001@192.168.0.33:5060></a>
Record-Route: <a class="moz-txt-link-rfc2396E" href="sip:192.168.0.1;lr=on"><sip:192.168.0.1;lr=on></a>
User-Agent: MAYAH 4.9.12.0-2.1.0.45
Content-Length: 0

And here the information from the opensips log files:

                Jun 22 14:30:32 localhost blox-0-9-6-beta[1975]:
ERROR:core:parse_cseq: no method found

Jun 22 14:30:32 localhost blox-0-9-6-beta[1975]: ERROR:core:parse_cseq:
bad cseq

Jun 22 14:30:32 localhost blox-0-9-6-beta[1975]:
ERROR:core:get_hdr_field: bad cseq

Perhaps someone of you knows this failure or can tell me how to solve
this problem?

Cheers,

Kai


</pre>
      </blockquote>
      <pre wrap="">

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a></pre>
  </body>
</html>