26 Oct
2007
26 Oct
'07
7:08 p.m.
Richard:
Sorry if this breaks threading, I don't have the original message.
In the cases where it doesn't work, can you confirm that the Contact
URI in the 200 actually contains a public address as it leaves your
network? What you're describing makes me think it's not, and it looks
like the following to me:
GW sends 200 with private address in Contact. This private address
leaks out of your network. This private address happens to fall
within the range of your customer's private network.
The 200 hits the remote router. The ALG leaves it alone (for now).
The PAP2T reads the Contact in the 200 and pulls the private address
from it. It targets the ACK to this private address, and sends it.
The ALG sees this, and notices the RURI contains a private address
from it's own local network. It PATs this address (hence the port
2021, it just picks the next port, since 2020 was already used by your
PAP2T). The ACK now contains the offending address in the RURI. When
your openser instance gets it, it just relays it like it was told to
do based on loose routing, and the call drops.
The thing about those ALGs is that they will rewrite *anything* that
matches the access list associated with the nat pool address, even if
it has nothing to do with any real IP traffic flowing through the
thing.
Hope that gives you something useful.
Phil
26 Oct
26 Oct
9:17 p.m.
New subject: [OpenSER-Users] ALG error workarounds
On Fri, 26 Oct 2007 18:08:14 +0200, Phil D'Amore <ptdamore(a)gmail.com>
wrote:
Richard:
Hi,
In the cases where it doesn't work, can you
confirm that the Contact
URI in the 200 actually contains a public address as it leaves your
network? What you're describing makes me think it's not, and it looks
like the following to me:
GW sends 200 with private address in Contact. This private address
leaks out of your network. This private address happens to fall
within the range of your customer's private network.
It doesn't seem to be that. Both the gateway and the proxy have public IPs
and no private ones.
The ALG sees this, and notices the RURI contains a
private address
from it's own local network. It PATs this address (hence the port
2021, it just picks the next port, since 2020 was already used by your
PAP2T). The ACK now contains the offending address in the RURI. When
your openser instance gets it, it just relays it like it was told to
do based on loose routing, and the call drops.>
The thing about those ALGs is that they will rewrite *anything* that
matches the access list associated with the nat pool address, even if
it has nothing to do with any real IP traffic flowing through the
thing.
Ok. Interesting to know how it does that.
In this case it doesn't seem to be that that is triggering the re-write
though.
I pasted the whole call trace at the end of this email, in case anyone
sees anything suspicious.
Thanks for thinking this through with me, and for any tips on how I could
detect and re-write these errors.
Richard.
Trace:
1.2.3.201 = Openser proxy
1.2.3.204 = Cisco gateway
81.1.2.218 = User agent IP.
U 81.1.2.218:2020 -> 1.2.3.201:5060
INVITE sip:00243999049102@sip.example.com SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-21460b8b.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 101 INVITE.
Max-Forwards: 70.
Contact: %5 <sip:101000000@81.1.2.218:2020>.
Expires: 240.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 252.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: x-sipura.
Content-Type: application/sdp.
.
v=0.
o=- 18539 18539 IN IP4 192.168.1.6.
s=-.
c=IN IP4 81.1.2.218.
t=0 0.
m=audio 16468 RTP/AVP 4 100 101.
a=rtpmap:4 G723/8000.
a=rtpmap:100 NSE/8000.
a=fmtp:100 192-193.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=sendrecv.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-21460b8b.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To:
<sip:00243999049102@sip.example.com>;tag=9df88149756df0cbffcc8c4447862715.8d93.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 101 INVITE.
Proxy-Authenticate: Digest realm="sip.example.com",
nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4".
Server: OpenSer (1.1.0-notls (i386/linux)).
Content-Length: 0.
Warning: 392 1.2.3.201:5060 "Noisy feedback tells: pid=15647
req_src_ip=81.1.2.218 req_src_port=2020
in_uri=sip:00243999049102@sip.example.com
out_uri=sip:00243999049102@sip.example.com via_cnt==1".
.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:00243999049102@sip.example.com SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-21460b8b.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To:
<sip:00243999049102@sip.example.com>;tag=9df88149756df0cbffcc8c4447862715.8d93.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 101 ACK.
Max-Forwards: 70.
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 81.1.2.218:2020 -> 1.2.3.201:5060
INVITE sip:00243999049102@sip.example.com SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 INVITE.
Max-Forwards: 70.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:00243999049102@sip.example.com",algorithm=MD5,response="e038a957ab555bc5a6734800164115b6".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
Expires: 240.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 252.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: x-sipura.
Content-Type: application/sdp.
.
v=0.
o=- 18539 18539 IN IP4 192.168.1.6.
s=-.
c=IN IP4 81.1.2.218.
t=0 0.
m=audio 16468 RTP/AVP 4 100 101.
a=rtpmap:4 G723/8000.
a=rtpmap:100 NSE/8000.
a=fmtp:100 192-193.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=sendrecv.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 INVITE.
Server: OpenSer (1.1.0-notls (i386/linux)).
Content-Length: 0.
Warning: 392 1.2.3.201:5060 "Noisy feedback tells: pid=15676
req_src_ip=81.1.2.218 req_src_port=2020
in_uri=sip:00243999049102@sip.example.com
out_uri=sip:202000243999049102@1.2.3.204 via_cnt==1".
.
U 1.2.3.201:5060 -> 1.2.3.204:5060
INVITE sip:202000243999049102@1.2.3.204 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 INVITE.
Max-Forwards: 69.
Contact: %5 <sip:101000000@81.1.2.218:2020>.
Expires: 240.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 252.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: x-sipura.
Content-Type: application/sdp.
.
v=0.
o=- 18539 18539 IN IP4 192.168.1.6.
s=-.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 100 101.
a=rtpmap:4 G723/8000.
a=rtpmap:100 NSE/8000.
a=fmtp:100 192-193.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=sendrecv.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow-Events: telephone-event.
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 183 Session Progress.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Disposition: session;handling=required.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 183 Session Progress.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Disposition: session;handling=required.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.0,SIP/2.0/UDP
81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.204.
t=0 0.
m=audio 17204 RTP/AVP 4 101.
c=IN IP4 1.2.3.204.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 1.2.3.201:5060 -> 81.1.2.218:2020
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-13d1535f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
Server: Cisco-SIPGateway/IOS-12.x.
CSeq: 102 INVITE.
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE,
NOTIFY, INFO, UPDATE, REGISTER.
Allow-Events: telephone-event.
Contact: <sip:202000243999049102@1.2.3.204:5060>.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Content-Type: application/sdp.
Content-Length: 294.
.
v=0.
o=CiscoSystemsSIP-GW-UserAgent 1869 2060 IN IP4 1.2.3.204.
s=SIP Call.
c=IN IP4 1.2.3.201.
t=0 0.
m=audio 61504 RTP/AVP 4 101.
c=IN IP4 1.2.3.201.
a=rtpmap:4 G723/8000.
a=fmtp:4 annexa=no.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:30.
a=direction:passive.
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2021
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bKf233.b0309086.2.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 69.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.204:51431 -> 1.2.3.201:5060
BYE sip:101000000@81.1.2.218:2020 SIP/2.0.
Via: SIP/2.0/UDP 1.2.3.204:5060;branch=z9hG4bKD3B675E.
From: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
To: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
User-Agent: Cisco-SIPGateway/IOS-12.x.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Timestamp: 1193399881.
CSeq: 101 BYE.
Content-Length: 0.
.
U 1.2.3.201:5060 -> 81.1.2.218:2020
BYE sip:101000000@81.1.2.218:2020 SIP/2.0.
Record-Route: <sip:1.2.3.201;lr=on;ftag=F48836B0-608>.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bK2333.35ada747.0.
Via: SIP/2.0/UDP 1.2.3.204:5060;branch=z9hG4bKD3B675E.
From: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
To: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
Date: Fri, 26 Oct 2007 11:57:22 GMT.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
User-Agent: Cisco-SIPGateway/IOS-12.x.
Max-Forwards: 69.
Timestamp: 1193399881.
CSeq: 101 BYE.
Content-Length: 0.
.
U 81.1.2.218:2020 -> 1.2.3.201:5060
SIP/2.0 200 OK.
To: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
From: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 101 BYE.
Via: SIP/2.0/UDP 1.2.3.201;branch=z9hG4bK2333.35ada747.0.
Via: SIP/2.0/UDP 1.2.3.204:5060;branch=z9hG4bKD3B675E.
Record-Route: <sip:1.2.3.201;lr=on;ftag=F48836B0-608>.
Timestamp: 1193399881.
Server: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
.
U 1.2.3.201:5060 -> 1.2.3.204:5060
SIP/2.0 200 OK.
To: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
From: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 101 BYE.
Via: SIP/2.0/UDP 1.2.3.204:5060;branch=z9hG4bKD3B675E.
Record-Route: <sip:1.2.3.201;lr=on;ftag=F48836B0-608>.
Timestamp: 1193399881.
Server: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
29 Oct
29 Oct
5:27 p.m.
New subject: [OpenSER-Users] ALG error workarounds
Hi,
Following on from last week's quest for the broken ALG fix in openser 1.1,
I am trying to re-write the ACK that replies to the 200 OK the gateway
sends when the call is connected, so that it arrives at the gateway
instead of being sent back to the sender.
This is the bad ACK:
gateway ip= 1.2.3.204
proxy ip= 1.2.3.201
ua ip = 81.1.2.218
U 81.1.2.218:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@81.1.2.218:2021 SIP/2.0.
Via: SIP/2.0/UDP 81.1.2.218:2020;branch=z9hG4bK-a8d9ae6f.
From: %5 <sip:101000000@sip.example.com>;tag=32750c901739579ao0.
To: <sip:00243999049102@sip.example.com>;tag=F48836B0-608.
Call-ID: da59b048-d5ba4742(a)192.168.1.6.
CSeq: 102 ACK.
Max-Forwards: 70.
Route: <sip:1.2.3.201;lr=on;ftag=32750c901739579ao0>.
Proxy-Authorization: Digest
username="101000000",realm="sip.example.com",nonce="4721d74d797d2fcdae92fc29db4798914ddb90a4",uri="sip:202000243999049102@81.1.2.218:2021",algorithm=MD5,response="d0a6ac0edaabb7fca6ef3ff448c7c4e1".
Contact: %5 <sip:101000000@81.1.2.218:2020>.
User-Agent: Linksys/PAP2T-3.1.15(LS).
Content-Length: 0.
What's wrong is that the uri should be:
ACK sip:202000243999049102@1.2.3.204:5060 SIP/2.0.
I can fix the problem like this:
if(src_ip==81.1.2.218 && method=="ACK" ){
rewritehostport("1.2.3.204:5060");
xlog("L_WARN", "rewritten host and port to: r-uri
<$ru> ");
}
But I really want to test (instead of src_ip==81.1.2.218) is whether the
URLs in square brackets match :
U [81.1.2.218]:2020 -> 1.2.3.201:5060
ACK sip:202000243999049102@[81.1.2.218]:2021 SIP/2.0.
How can I test that in 1.1?
Thanks for your help.
Richard
5:56 p.m.
New subject: [OpenSER-Users] Enum lookup delays
I'm having some real problems with enum lookup delays (20 or 30 seconds
before they come back) I'm using e164.arpa then nrenum.net, these seem
to have worked fine until yesterday evening it seems...
Does anyone have any info on whether either of these services is having
problems???
30 Oct
30 Oct
9:30 a.m.
New subject: [OpenSER-Users] Enum lookup delays
Hi Nick!
This is a known problem with ENUM - lame delegations will increase DNS
lookup duration and you can't avoid it (it also happened to e164.arpa
last year when Italy's name server were offline).
You should adjust DNS timeouts (see core cookbook on openser wiki) and
make sure to reply with 100 trying before the ENUM lookup.
regards
klaus
Nick Warr schrieb:
I'm having some real problems with enum lookup
delays (20 or 30 seconds
before they come back) I'm using e164.arpa then nrenum.net, these seem
to have worked fine until yesterday evening it seems...
Does anyone have any info on whether either of these services is having
problems???
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
5:43 p.m.
New subject: [OpenSER-Users] Enum lookup delays
Klaus Darilion schrieb:
Hi Nick!
This is a known problem with ENUM - lame delegations will increase DNS
lookup duration and you can't avoid it (it also happened to e164.arpa
last year when Italy's name server were offline).
Hi! It is again Italy:
dig 1.2.3.9.3.e164.arpa naptr +trace
; <<>> DiG 9.2.4 <<>> 1.2.3.9.3.e164.arpa naptr +trace
;; global options: printcmd
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS L.ROOT-SERVERS.NET.
. 518400 IN NS M.ROOT-SERVERS.NET.
. 518400 IN NS A.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NET.
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS J.ROOT-SERVERS.NET.
;; Received 244 bytes from 83.136.32.190#53(83.136.32.190) in 23 ms
e164.arpa. 172800 IN NS ns0.verio.net.
e164.arpa. 172800 IN NS sec3.apnic.net.
e164.arpa. 172800 IN NS sunic.sunet.se.
e164.arpa. 172800 IN NS ns-pri.ripe.net.
e164.arpa. 172800 IN NS tinnie.arin.net.
e164.arpa. 172800 IN NS e164-arpa.cnnic.net.cn.
;; Received 205 bytes from 193.0.14.129#53(K.ROOT-SERVERS.NET) in 30 ms
9.3.e164.arpa. 14400 IN NS dns2.istsupcti.it.
9.3.e164.arpa. 14400 IN NS dns.istsupcti.it.
;; Received 86 bytes from 192.102.248.135#53(ns0.verio.net) in 159 ms
;; connection timed out; no servers could be reached
As a workaround you can configure the Italien zone 9.3.e164.arpa in your
resolver.
regards
Klaus
You should adjust DNS timeouts (see core cookbook on openser wiki) and
make sure to reply with 100 trying before the ENUM lookup.
regards
klaus
Nick Warr schrieb:
I'm having some real problems with enum
lookup delays (20 or 30 seconds
before they come back) I'm using e164.arpa then nrenum.net, these seem
to have worked fine until yesterday evening it seems...
Does anyone have any info on whether either of these services is having
problems???
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
6236
days inactive
6240
days old
5 comments
4 participants
participants (4)
-
Klaus Darilion -
Nick Warr -
Phil D'Amore -
Richard Bennett