[Serusers] REGISTER message headers verification
Aisling O'Driscoll
ashling.odriscoll at cit.ie
Wed Nov 30 19:07:49 CET 2005
Hi,
I was wondering if someone could please cast their eyes over the
register sent from one of my phones behind a nat and the 200 OK sent
back from SER.
There has been an issue with no audio between a natted client and a
public client. I looked at the invite and noticed the private address
was being used in the Contact header field and the c field in the sdp
so obviously the headers are not being rewritten properly....I then
checked the register messages to see if the phone was registering
correctly - The message sequence is below. I notice the private
header is shown but that would probably be correct seeing
fix_nated_register doesnt actually change the header, it simply adds
fields, is that right? i.e. thats why it replaced fix_nated-contact
to be more RFC compliant
Anyway its the contact header fields sent back in the 200OK that I
would like verified - Should the private address be listed as one of
the options here?
I have gone back to the onsip feature callfwd script using mediaproxy
to eliminate any errors due to changes I may have made The ONLY
difference between the scripts is that I have
if(uri != myself)
{
route(4);
route(1);
break;
};
instead of
#if (!is_uri_host_local()) {
# if (is_from_local() || allow_trusted()) {
# route(4);
# route(1);
# } else {
# sl_send_reply("403", "Forbidden");
# };
# break;
# };
as otherwise the phones wouldn't register.
Many thanks,
Aisling.
SER: 157.190.74.152
Phone Private Address: 172.16.3.13
NAT Box: 84.203.148.14
U 84.203.148.14:5060 -> 157.190.74.152:5060
REGISTER sip:157.190.74.152:5060 SIP/2.0..Via: SIP/2.0/UDP
172.16.3.13;bran
ch=z9hG4bK7543671c6ca1f07a..From: "Aisling 2092"
<sip:2092 at 157.190.74.152:5
060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5060>..Contact: <si
p:2092 at 172.16.3.13>..Call-ID: 78f22336c383663f at 172.16.3.13..CSeq:
100 REGIS
TER..Expires: 3456000..User-Agent: Grandstream BT100
1.0.6.7..Max-Forwards:
70..Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Cont
ent-Length: 0....
#
U 157.190.74.152:5060 -> 84.203.148.14:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP
172.16.3.13;branch=z9hG4bK7543671c6ca1
f07a;received=84.203.148.14..From: "Aisling 2092"
<sip:2092 at 157.190.74.152:
5060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5060>..Call-ID: 78
f22336c383663f at 172.16.3.13..CSeq: 100 REGISTER..Server: Sip EXpress
router
(0.9.4 (i386/linux))..Content-Length: 0..Warning: 392
157.190.74.152:5060 "
Noisy feedback tells: pid=1742 req_src_ip=84.203.148.14
req_src_port=5060
in_uri=sip:157.190.74.152:5060 out_uri=sip:157.190.74.152:5060
via_cnt==1".
...
#
U 157.190.74.152:5060 -> 84.203.148.14:5060
SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP
172.16.3.13;branch=z9hG4bK754367
1c6ca1f07a;rport=5060;received=84.203.148.14..From: "Aisling 2092"
<sip:209
2 at 157.190.74.152:5060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5
060>;tag=4b358c93636b59b9f78eca99791ec991.cdd2..Call-ID:
78f22336c383663f at 1
72.16.3.13..CSeq: 100 REGISTER..WWW-Authenticate: Digest
realm="157.190.74.
152", nonce="438dfc0821fd70b65dbd9c0db3e5aa29fa1fcd82"..Server: Sip
EXpress
router (0.9.4 (i386/linux))..Content-Length: 0..Warning: 392
157.190.74.15
2:5060 "Noisy feedback tells: pid=1742 req_src_ip=84.203.148.14
req_src_po
rt=5060 in_uri=sip:157.190.74.152:5060
out_uri=sip:157.190.74.152:5060 via_
cnt==1"....
#
U 84.203.148.14:5060 -> 157.190.74.152:5060
REGISTER sip:157.190.74.152:5060 SIP/2.0..Via: SIP/2.0/UDP
172.16.3.13;bran
ch=z9hG4bK9e94983538147a54..From: "Aisling 2092"
<sip:2092 at 157.190.74.152:5
060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5060>..Contact: <si
p:2092 at 172.16.3.13>..Authorization: Digest username="2092",
realm="157.190.
74.152", algorithm=MD5, uri="sip:157.190.74.152:5060",
nonce="438dfc0821fd7
0b65dbd9c0db3e5aa29fa1fcd82",
response="90d926c009567996b99e76fef560b9c6"..
Call-ID: 78f22336c383663f at 172.16.3.13..CSeq: 101 REGISTER..Expires:
3456000
..User-Agent: Grandstream BT100 1.0.6.7..Max-Forwards: 70..Allow:
INVITE,AC
K,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Length:
0....
#
U 157.190.74.152:5060 -> 84.203.148.14:5060
SIP/2.0 100 Trying..Via: SIP/2.0/UDP
172.16.3.13;branch=z9hG4bK9e9498353814
7a54;received=84.203.148.14..From: "Aisling 2092"
<sip:2092 at 157.190.74.152:
5060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5060>..Call-ID: 78
f22336c383663f at 172.16.3.13..CSeq: 101 REGISTER..Server: Sip EXpress
router
(0.9.4 (i386/linux))..Content-Length: 0..Warning: 392
157.190.74.152:5060 "
Noisy feedback tells: pid=1744 req_src_ip=84.203.148.14
req_src_port=5060
in_uri=sip:157.190.74.152:5060 out_uri=sip:157.190.74.152:5060
via_cnt==1".
...
#
U 157.190.74.152:5060 -> 84.203.148.14:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP
172.16.3.13;branch=z9hG4bK9e94983538147a54
;rport=5060;received=84.203.148.14..From: "Aisling 2092"
<sip:2092 at 157.190.
74.152:5060>;tag=2ec993227a53039b..To:
<sip:2092 at 157.190.74.152:5060>;tag=4
b358c93636b59b9f78eca99791ec991.3e0a..Call-ID:
78f22336c383663f at 172.16.3.13
..CSeq: 101 REGISTER..Contact:
<sip:2092 at 157.190.74.151>;expires=3279337, <
sip:2092 at 172.16.3.13>;expires=3447275;received="sip:84.203.148.14:50
60", <s
ip:2092 at 84.203.148.14:5060>;expires=3456000..Server: Sip EXpress
router (0.
9.4 (i386/linux))..Content-Length: 0..Warning: 392
157.190.74.152:5060 "Noi
sy feedback tells: pid=1744 req_src_ip=84.203.148.14
req_src_port=5060 in_
uri=sip:157.190.74.152:5060 out_uri=sip:157.190.74.152:5060
via_cnt==1"....
##exit
91 received, 0 dropped
localhost:~ #
-------------------Legal Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
More information about the sr-users
mailing list