Hey, considering that you get free help, culminating with the fact you have almost 0 knowledge in basic stuff (like making a simple network capture), I would not complain AT ALL about taking too long. So please be at least grateful for the help you get.

The problem is your setup - to spare some time, you should mention that you actually run opensips behind NAT and you receive traffic from public internet. OpenSIPS is adding a RR header with a private IP which is not routable from the caller side (public internet), so caller cannot fire the ACK as response to the received 200 OK.

So, your setup is bogus.

Regards,
Bogdan

On 03/16/2012 04:40 PM, talha jilal wrote:
Hi,

Here you find output ,

http://pastebin.com/ivWcFaXi

Thanks for your help, can I get reply soon. Its taking too long.


Thanks !
------------------------------------------------------------------------
Date: Fri, 16 Mar 2012 13:52:36 +0200
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Users Digest, Vol 44, Issue 25

Hi,

To get ngrep to filter the capturing on "300" do :
    ngrep -d any -W byline -t *300* port 5060

upload the output somewhere on pastebin or similar - this mailing list is limited to attachments of 40K.

Regards,
Bogdan

On 03/15/2012 04:54 PM, talha jilal wrote:


    Hello Bogdan,


    Here is my ngrep output, for only 300 extension where I am
    calling.  I also attached ngrep full out put from when I start
    calling till end.




    To: <sip:[email protected];user=phone>;tag=4249013220.
    Contact: "300" <sip:[email protected]:5060;transport=udp>.
    i="300"<sip:>.
    a=X-NameLabel:300.
    To: <sip:[email protected];user=phone>;tag=4249013220.
    Contact: "300" <sip:[email protected]:5060;transport=udp>.
    i="300"<sip:>.

    ^C

    *
    *
    *
    *
    *Thanks !
    Talha Jilal

    *

    ------------------------------------------------------------------------
    Date: Wed, 14 Mar 2012 14:22:23 +0200
    From: [email protected] <mailto:[email protected]>
    To: [email protected] <mailto:[email protected]>
    CC: [email protected] <mailto:[email protected]>
    Subject: Re: Users Digest, Vol 44, Issue 25

    I mentioned ngrep, not grep :D .

    Do :
        ngrep -d any -W byline -t . port 5060

    Regards,
    Bogdan

    On 03/12/2012 08:54 PM, talha jilal wrote:


        Hi,


        Here is output with grep

        Please advise me full command if I am doing some thing wrong,
        I am using  centos 6.0 32 bit.



        -bash-4.1#  tcpdump -i eth2 -n -s0 -vvv tcp  port 5060  | grep 300
        tcpdump: listening on eth2, link-type EN10MB (Ethernet),
        capture size 65535 bytes



        07:51:21.257355 IP (tos 0x0, ttl 118, id 27728, offset 0,
        flags [DF], proto TCP (6), length 1300)
        07:51:27.511152 IP (tos 0x10, ttl 64, id 6173, offset 0, flags
        [DF], proto TCP (6), length 1300)
        07:51:28.015258 IP (tos 0x10, ttl 64, id 6175, offset 0, flags
        [DF], proto TCP (6), length 1300)
        07:51:29.022329 IP (tos 0x10, ttl 64, id 6177, offset 0, flags
        [DF], proto TCP (6), length 1300)




        Thanks

        ------------------------------------------------------------------------
        Date: Mon, 12 Mar 2012 20:30:10 +0200
        From: [email protected] <mailto:[email protected]>
        To: [email protected] <mailto:[email protected]>;
        [email protected] <mailto:[email protected]>
        Subject: Re: Users Digest, Vol 44, Issue 25

        Hi,

        1) please keep the list at CC all the time !

        2) the tcpdump output is no enough - use ngrep as I need to
        see the actual content of the SIP package ; or make a pcap
        capture and upload it somewhere for download.

        Regards,
        Bogdan


--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to