Re: [Serusers] why would a client behave differently for nat onoutbound as opposed to inbound

5 Apr 2005

I'm not really familiar with the various mediaproxy client tests, but I 
assume it's ok.  Have you tried to add a log or xlog command inside the test 
to make sure it is run for both?  You need use_media_proxy() somewhere 
(inside a test for method=="INVITE")?!

The Getting Started document at http://ONsip.org/ and corresponding 
mediaproxy.cfg should be a good reference.
g-)

Iqbal wrote:
...
  if (client_nat_test("3")) {
                setflag(15);
                force_rport();
                fix_nated_contact();
        };

        if (isflagset(15) && !search("^Record-Route:")) {
                force_rport();
                fix_contact();
        };

 this is the intial fix for ALL invite requests, after which I do the
 processing based on dialed prefix etc, hence if xlite is processed via
 this, and fixed I guess HT should also, would be fix_nated_register on
 the REGISTER request do anything to this. I dont think so, but...I
 have been known to be wrong :-), Also do I need to dont i need a fix
 sdp somewhere...

 Iqbal

 Greger V. Teigre wrote:

> I cannot really say. How do you test incoming INVITEs in ser.cfg?
> g-)
>
> Iqbal wrote:
>
>> Hi
>>
>> Thats wat i thought, but since the same ser.cfg is being used :-)
>> why wouldnt HT be proxied, surely the ser.cfg reads the INVITE and
>> processes it the same for HT and for xlite, why would it differ
>> based on the client used.
>>
>> Iqbal
>>
>> Greger V. Teigre wrote:
>>
>>> Ok, this is what I see (assuming you *want* to proxy the call) :
>>> - HT is not proxied. This means that your ser.cfg does not detect
>>> the private address in the SDP and the SDP payload is not
>>> rewritten in an incoming INVITE (use_media_proxy() was not
>>> called).  Have a look at the code detecting NAT for INVITEs.
>>> - Xlite is proxied, so you correctly detect the NAT in the
>>> onreply_route. g-)
>>>
>>> Iqbal wrote:
>>>
>>>> Hi
>>>>
>>>> Heres the trace
>>>>
>>>> NOTE : Internal IP are exactly how they are, external been search
>>>> and replaced. Taken using ngrep
>>>>
>>>> ----------
>>>> ###########
>>>> U 2005/04/03 16:14:47.352103 223.78.240.109:1024 ->
>>>> 201.218.150.25:5060 INVITE sip:040600@sip.domain.com SIP/2.0.
>>>> Via: SIP/2.0/UDP 192.168.20.3;branch=z9hG4bK6afda005df28ce2f.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>.
>>>> Contact: <sip:040618@192.168.20.3>.
>>>> Supported: replaces.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15178 INVITE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 70.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Type: application/sdp.
>>>> Content-Length: 340.
>>>> .
>>>> v=0.
>>>> o=040618 8000 0 IN IP4 192.168.20.3.
>>>> s=SIP Call.
>>>> c=IN IP4 192.168.20.3.
>>>> t=0 0.
>>>> m=audio 5004 RTP/AVP 0 8 4 18 2 15 99.
>>>> a=sendrecv.
>>>> a=rtpmap:0 PCMU/8000/3.
>>>> a=rtpmap:8 PCMA/8000/3.
>>>> a=rtpmap:4 G723/8000/3.
>>>> a=rtpmap:18 G729/8000/3.
>>>> a=rtpmap:2 G726-32/8000/3.
>>>> a=rtpmap:15 G728/8000/3.
>>>> a=rtpmap:99 iLBC/8000/3.
>>>> a=fmtp:99 mode=20.
>>>> a=ptime:20.
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.390154 201.218.150.25:5060 ->
>>>> 223.78.240.109:1024 SIP/2.0 407 Proxy Authentication Required.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;branch=z9hG4bK6afda005df28ce2f;rport=1024;received=223.78.240.109.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To:
>>>>
<sip:040600@sip.domain.com>;tag=bde2d0f39a3c31098b0c0a337d26256c.5b34.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15178 INVITE.
>>>> Proxy-Authenticate: Digest realm="sip.domain.com",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed".
>>>> Content-Length: 0.
>>>> Warning: 392 201.218.150.25:5060 "Noisy feedback tells:  pid=2783
>>>> req_src_ip=223.78.240.109 req_src_port=1024
>>>> in_uri=sip:040600@sip.domain.com
>>>> out_uri=sip:040600@223.78.240.109:5060 via_cnt==1".
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.439305 223.78.240.109:1024 ->
>>>> 201.218.150.25:5060 ACK sip:040600@sip.domain.com SIP/2.0.
>>>> Via: SIP/2.0/UDP 192.168.20.3;branch=z9hG4bK6afda005df28ce2f.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To:
>>>>
<sip:040600@sip.domain.com>;tag=bde2d0f39a3c31098b0c0a337d26256c.5b34.
>>>> Contact: <sip:040618@192.168.20.3>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15178 ACK.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 70.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.479407 223.78.240.109:1024 ->
>>>> 201.218.150.25:5060 INVITE sip:040600@sip.domain.com SIP/2.0.
>>>> Via: SIP/2.0/UDP 192.168.20.3;branch=z9hG4bK1884d89b14226d43.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>.
>>>> Contact: <sip:040618@192.168.20.3>.
>>>> Supported: replaces.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@sip.domain.com",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="d4573559ec2e355755de825d8afb4a1f".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 70.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Type: application/sdp.
>>>> Content-Length: 340.
>>>> .
>>>> v=0.
>>>> o=040618 8000 1 IN IP4 192.168.20.3.
>>>> s=SIP Call.
>>>> c=IN IP4 192.168.20.3.
>>>> t=0 0.
>>>> m=audio 5004 RTP/AVP 0 8 4 18 2 15 99.
>>>> a=sendrecv.
>>>> a=rtpmap:0 PCMU/8000/3.
>>>> a=rtpmap:8 PCMA/8000/3.
>>>> a=rtpmap:4 G723/8000/3.
>>>> a=rtpmap:18 G729/8000/3.
>>>> a=rtpmap:2 G726-32/8000/3.
>>>> a=rtpmap:15 G728/8000/3.
>>>> a=rtpmap:99 iLBC/8000/3.
>>>> a=fmtp:99 mode=20.
>>>> a=ptime:20.
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.516822 201.218.150.25:5060 ->
>>>> 223.78.240.109:1024 SIP/2.0 100 trying -- your call is important
>>>> to us.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;branch=z9hG4bK1884d89b14226d43;rport=1024;received=223.78.240.109.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Content-Length: 0.
>>>> Warning: 392 201.218.150.25:5060 "Noisy feedback tells:  pid=2786
>>>> req_src_ip=223.78.240.109 req_src_port=1024
>>>> in_uri=sip:040600@sip.domain.com
>>>> out_uri=sip:040600@223.78.240.109:5060 via_cnt==1".
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.517367 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 INVITE sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bKe94c.0d901766.0.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>.
>>>> Contact: <sip:040618@223.78.240.109:1024>.
>>>> Supported: replaces.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@sip.domain.com",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="d4573559ec2e355755de825d8afb4a1f".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 16.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Type: application/sdp.
>>>> Content-Length: 340.
>>>> .
>>>> v=0.
>>>> o=040618 8000 1 IN IP4 192.168.20.3.
>>>> s=SIP Call.
>>>> c=IN IP4 192.168.20.3.
>>>> t=0 0.
>>>> m=audio 5004 RTP/AVP 0 8 4 18 2 15 99.
>>>> a=sendrecv.
>>>> a=rtpmap:0 PCMU/8000/3.
>>>> a=rtpmap:8 PCMA/8000/3.
>>>> a=rtpmap:4 G723/8000/3.
>>>> a=rtpmap:18 G729/8000/3.
>>>> a=rtpmap:2 G726-32/8000/3.
>>>> a=rtpmap:15 G728/8000/3.
>>>> a=rtpmap:99 iLBC/8000/3.
>>>> a=fmtp:99 mode=20.
>>>> a=ptime:20.
>>>>
>>>> #
>>>> U 2005/04/03 16:14:47.968715 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 INVITE sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bKe94c.0d901766.0.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>.
>>>> Contact: <sip:040618@223.78.240.109:1024>.
>>>> Supported: replaces.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@sip.domain.com",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="d4573559ec2e355755de825d8afb4a1f".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 16.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Type: application/sdp.
>>>> Content-Length: 340.
>>>> .
>>>> v=0.
>>>> o=040618 8000 1 IN IP4 192.168.20.3.
>>>> s=SIP Call.
>>>> c=IN IP4 192.168.20.3.
>>>> t=0 0.
>>>> m=audio 5004 RTP/AVP 0 8 4 18 2 15 99.
>>>> a=sendrecv.
>>>> a=rtpmap:0 PCMU/8000/3.
>>>> a=rtpmap:8 PCMA/8000/3.
>>>> a=rtpmap:4 G723/8000/3.
>>>> a=rtpmap:18 G729/8000/3.
>>>> a=rtpmap:2 G726-32/8000/3.
>>>> a=rtpmap:15 G728/8000/3.
>>>> a=rtpmap:99 iLBC/8000/3.
>>>> a=fmtp:99 mode=20.
>>>> a=ptime:20.
>>>>
>>>> ####
>>>> U 2005/04/03 16:14:49.718507 223.78.240.109:5060 ->
>>>> 201.218.150.25:5060 SIP/2.0 100 Trying.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bKe94c.0d901766.0.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:50.478983 223.78.240.109:5060 ->
>>>> 201.218.150.25:5060 SIP/2.0 180 Ringing.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bKe94c.0d901766.0.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:50.480364 201.218.150.25:5060 ->
>>>> 223.78.240.109:1024 SIP/2.0 180 Ringing.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> ############
>>>> U 2005/04/03 16:14:54.716498 223.78.240.109:5060 ->
>>>> 201.218.150.25:5060 SIP/2.0 200 Ok.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bKe94c.0d901766.0.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Content-Type: application/sdp.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 200.
>>>> .
>>>> v=0.
>>>> o=040600 152816778 152823799 IN IP4 223.78.240.109.
>>>> s=X-Lite.
>>>> c=IN IP4 223.78.240.109.
>>>> t=0 0.
>>>> m=audio 8000 RTP/AVP 3 101.
>>>> a=rtpmap:3 gsm/8000.
>>>> a=rtpmap:101 telephone-event/8000.
>>>> a=fmtp:101 0-15.
>>>>
>>>> #
>>>> U 2005/04/03 16:14:54.719442 201.218.150.25:5060 ->
>>>> 223.78.240.109:1024 SIP/2.0 200 Ok.
>>>> Via: SIP/2.0/UDP
>>>>
192.168.20.3;rport=1024;received=223.78.240.109;branch=z9hG4bK1884d89b14226d43.
>>>>
>>>>
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Record-Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 INVITE.
>>>> Content-Type: application/sdp.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 200.
>>>> .
>>>> v=0.
>>>> o=040600 152816778 152823799 IN IP4 223.78.240.109.
>>>> s=X-Lite.
>>>> c=IN IP4 223.78.240.109.
>>>> t=0 0.
>>>> m=audio 8000 RTP/AVP 3 101.
>>>> a=rtpmap:3 gsm/8000.
>>>> a=rtpmap:101 telephone-event/8000.
>>>> a=fmtp:101 0-15.
>>>>
>>>> #
>>>> U 2005/04/03 16:14:54.801450 223.78.240.109:1024 ->
>>>> 201.218.150.25:5060 ACK sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Via: SIP/2.0/UDP 192.168.20.3;branch=z9hG4bK6044f43b5006eedc.
>>>> Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040618@192.168.20.3>.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@223.78.240.109:5060",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="ca8ea99e9b8345bde6ccb263ffd5a038".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 ACK.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 70.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:14:54.803421 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 ACK sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Record-Route: <sip:201.218.150.25;ftag=a660434c00b83084;lr=on>.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=0.
>>>> Via: SIP/2.0/UDP
>>>> 192.168.20.3;received=223.78.240.109;branch=z9hG4bK6044f43b5006eedc.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040618@192.168.20.3>.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@223.78.240.109:5060",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="ca8ea99e9b8345bde6ccb263ffd5a038".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15179 ACK.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 16.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #########
>>>> U 2005/04/03 16:15:00.913249 223.78.240.109:1024 ->
>>>> 201.218.150.25:5060 BYE sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Via: SIP/2.0/UDP 192.168.20.3;branch=z9hG4bK1527872e4e616368.
>>>> Route:
>>>>
<sip:040600@201.218.150.25:5060;nat=yes;ftag=a660434c00b83084;lr=on>.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@223.78.240.109:5060",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="5fd8e1f30a2924a53e44f8e9ad0abf47".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15180 BYE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 70.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:15:00.948553 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 BYE sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Record-Route: <sip:201.218.150.25;ftag=a660434c00b83084;lr=on>.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bK4a4c.3281602.0.
>>>> Via: SIP/2.0/UDP
>>>> 192.168.20.3;received=223.78.240.109;branch=z9hG4bK1527872e4e616368.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@223.78.240.109:5060",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="5fd8e1f30a2924a53e44f8e9ad0abf47".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15180 BYE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 16.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:15:00.993724 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 BYE sip:040600@223.78.240.109:5060 SIP/2.0.
>>>> Record-Route: <sip:201.218.150.25;ftag=a660434c00b83084;lr=on>.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bK4a4c.3281602.0.
>>>> Via: SIP/2.0/UDP
>>>> 192.168.20.3;received=223.78.240.109;branch=z9hG4bK1527872e4e616368.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Proxy-Authorization: DIGEST username="040618",
>>>> realm="sip.domain.com", algorithm=MD5,
>>>> uri="sip:040600@223.78.240.109:5060",
>>>> nonce="42500993cb56f08d341fb7a29897c97250e955ed",
>>>> response="5fd8e1f30a2924a53e44f8e9ad0abf47".
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15180 BYE.
>>>> User-Agent: Grandstream HT487 1.0.5.18.
>>>> Max-Forwards: 16.
>>>> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:15:01.086530 223.78.240.109:5060 ->
>>>> 201.218.150.25:5060 SIP/2.0 200 Ok.
>>>> Via: SIP/2.0/UDP 201.218.150.25;branch=z9hG4bK4a4c.3281602.0.
>>>> Via: SIP/2.0/UDP
>>>> 192.168.20.3;received=223.78.240.109;branch=z9hG4bK1527872e4e616368.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15180 BYE.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> #
>>>> U 2005/04/03 16:15:01.087731 201.218.150.25:5060 ->
>>>> 223.78.240.109:5060 SIP/2.0 200 Ok.
>>>> Via: SIP/2.0/UDP
>>>> 192.168.20.3;received=223.78.240.109;branch=z9hG4bK1527872e4e616368.
>>>> From: "Iqbal"
<sip:040618@sip.domain.com>;tag=a660434c00b83084.
>>>> To: <sip:040600@sip.domain.com>;tag=1718523.
>>>> Contact: <sip:040600@223.78.240.109:5060>.
>>>> Call-ID: fdef3f406ba21473(a)192.168.20.3.
>>>> CSeq: 15180 BYE.
>>>> Server: X-Lite release 1103m.
>>>> Content-Length: 0.
>>>> .
>>>>
>>>> ###############
>>>>
>>>> ---------------------
>>>>
>>>>
>>>> On 4/3/2005, "Greger V. Teigre" &lt;greger(a)teigre.com&gt;
wrote:
>>>>
>>>>> Iqbal,
>>>>> post a trace of the INVITE and OK going from HT to xlite (taken
>>>>> on the SER server).
>>>>> g-)
>>>>>
>>>>> Iqbal wrote:
>>>>>
>>>>>> Couldnt think of a better subject, basically I have a handytone
>>>>>> (HT) , and a xlite behind the same router, which is natting. SER
>>>>>> is external
>>>>>>
>>>>>> Now when I call HT to xlite I hear absolutely nothing in either
>>>>>> direction, and nuthing except for a request from xlite hits the
>>>>>> mediaproxy...but when xlite calls HT, mediaproxy lights up like
>>>>>> a xmas tree, and all is well.
>>>>>>
>>>>>> What I can see is that if the router is the same one, then
>>>>>> surely something in the HT settings (I have no NAT traversal
>>>>>> set in HT) causing this, or something in xlite telling it what
>>>>>> to do, I just cant see what.
>>>>>>
>>>>>> Oh xlite/HT to pstn works fine, and inbound from pstn to
>>>>>> HT/xlite is also fine voice both ways.
>>>>>>
>>>>>> Iqbal
>>>>>>
>>>>>> _______________________________________________
>>>>>> Serusers mailing list
>>>>>> serusers(a)lists.iptel.org
>>>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>>
>>>>>
>>>
>>>
>>> .
>>
>
>
> .  

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Re: [Serusers] why would a client behave differently for nat onoutbound as opposed to inbound