27 Feb
2006
27 Feb
'06
2:38 p.m.
Hi,
How to disable sending Contact HF in OK send to a successful (i.e.
authenticated) REGISTER request?
Just use remove_hf() from textops or there is other option?
I've got stupid UA that behaves badly when working behind NAT. First it
sends REGISTER without anything (no Contact, Expires). On successful
authentication SER responds 200 OK with Contact HF, set to public IP,
exactly how SER sees UA behind NAT (like some_IP:61001).
Then the stupid UA sends another REGISTER message, this time with
Contact and Via HF set to this public value (i.e. some_IP:61001).
It spoils my nathelper/rtpproxy detection of devices behind NAT.
Of course I can enable it by regexp on User-Agent HF, but his is not an
option, as plenty of those UAs runs not behind NAT.
--
Regards,
Arek Bekiersz
1 Mar
1 Mar
11:40 a.m.
Arek Bekiersz wrote:
Hi,
How to disable sending Contact HF in OK send to a successful (i.e.
authenticated) REGISTER request?
Use:
save_noreply("location");
sl_send_reply("200", "OK");
This will send 200 OK without Contacts.
Jan.
Just use remove_hf() from textops or there is other
option?
I've got stupid UA that behaves badly when working behind NAT. First it
sends REGISTER without anything (no Contact, Expires). On successful
authentication SER responds 200 OK with Contact HF, set to public IP,
exactly how SER sees UA behind NAT (like some_IP:61001).
Then the stupid UA sends another REGISTER message, this time with
Contact and Via HF set to this public value (i.e. some_IP:61001).
It spoils my nathelper/rtpproxy detection of devices behind NAT.
Of course I can enable it by regexp on User-Agent HF, but his is not an
option, as plenty of those UAs runs not behind NAT.
4:21 p.m.
Jan,
Thanks for tip. I forgot to read manual.
:-)))
I tried. But the problem persist
:-(((
The stupid UA keeps sending public IP in Via and Contact, when behind
NAT. It is learning his public IP from Via. Or I don't know how. Magic?
Here is the registration sequence seen from LAN. UA has IP 192.168.1.200
in private LAN behind NAT. NAT maps UAs port 5060 in LAN to port 61003
in WAN:
192.168.1.200:5060 -> proxy_wan_ip:5060
REGISTER sip:proxy_realm SIP/2.0
Via: SIP/2.0/UDP
192.168.1.200:5060;branch=z9hG4bKD87C4E6B9057BD25A6EC854BAEB4F
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>
Call-ID: foo
CSeq: 1 REGISTER
Max-Forwards: 70
User-Agent: stupid-user-agent
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO,
SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0
proxy_wan_ip:5060 -> 192.168.1.200:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
192.168.1.200:5060;branch=z9hG4bKD87C4E6B9057BD25A6EC854BAEB4F;rport=61003;received=nat_wan_ip
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>;tag=935ab969d5b642f019e17a3a52b4e4b2.8ec3
Call-ID: 31888733A35E0EFE3FC22B073B50C(a)192.168.1.200
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="proxy_realm",
nonce="4405aadab124f8b271a6d6282a0fd9abc4b09b8e"
Server: Sip EXpress router
Content-Length: 0
192.168.1.200:5060 -> proxy_wan_ip:5060
REGISTER sip:proxy_realm SIP/2.0
Via: SIP/2.0/UDP
nat_wan_ip:61003;branch=z9hG4bK7BB67339C326394708852DEC41F3C
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>
Call-ID: foo
CSeq: 2 REGISTER
Authorization: Digest username="1234", realm="proxy_realm",
nonce="4405aadab124f8b271a6d6282a0fd9abc4b09b8e",
uri="sip:proxy_realm",
response="5a5c8fd5e58aa3cdcaff214c5ae4d2aa"
Max-Forwards: 70
User-Agent: stupid-user-agent
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO,
SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0
proxy_wan_ip:5060 -> 192.168.1.200:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP
nat_wan_ip:61003;branch=z9hG4bK7BB67339C326394708852DEC41F3C
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>;tag=935ab969d5b642f019e17a3a52b4e4b2.1a9c
Call-ID: foo
CSeq: 2 REGISTER
Server: Sip EXpress router
Content-Length: 0
192.168.1.200:5060 -> proxy_wan_ip:5060
REGISTER sip:proxy_realm SIP/2.0
[WRONG!!] Via: SIP/2.0/udp
nat_wan_ip:61003;branch=z9hG4bK82B006EB79CB30C39996A78C9962D
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>
Call-ID: foo
CSeq: 3 REGISTER
[WRONG!!] Contact:
<sip:1234@nat_wan_ip:61003;uniq=0FC6DA2B97704905AA040333C2B03>
Authorization: Digest username="1234", realm="proxy_realm",
nonce="4405aadab124f8b271a6d6282a0fd9abc4b09b8e",
uri="sip:proxy_realm",
response="5a5c8fd5e58aa3cdcaff214c5ae4d2aa"
Expires: 1800
Max-Forwards: 70
User-Agent: stupid-user-agent
Supported: 100rel, replaces
Allow-Events: telephone-event, refer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, UPDATE, PRACK, INFO,
SUBSCRIBE, NOTIFY, REFER, MESSAGE
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 0
proxy_wan_ip:5060 -> 192.168.1.200:5060
SIP/2.0 200 OK
Via: SIP/2.0/udp
nat_wan_ip:61003;branch=z9hG4bK82B006EB79CB30C39996A78C9962D
From: <sip:1234@proxy_realm>;tag=2789838218
To: <sip:1234@proxy_realm>;tag=935ab969d5b642f019e17a3a52b4e4b2.3770
Call-ID: 31888733A35E0EFE3FC22B073B50C(a)192.168.1.200
CSeq: 3 REGISTER
Server: Sip EXpress router
Content-Length: 0
--
Regards,
Arek Bekiersz
6841
days inactive
6843
days old
2 comments
2 participants
participants (2)
-
Arek Bekiersz -
Jan Janak