rendered paste bodyContent-Length: 0
<------------>
Scheduling destruction of SIP dialog '655233566_29683279@4.55.17.35' in 32000 ms (Method: INVITE)
<--- SIP read from UDP:216.115.69.144:5060 --->
ACK sip:12012156850@192.168.0.35:5061 SIP/2.0
To: <sip:+12012156850@flowroute.com>;tag=as2a39ba40
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK0e21e5bc
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK543a.8f7f27dd5db7679f1183fa4880fde7ed.0
Call-ID: 655233566_29683279@4.55.17.35
CSeq: 28121 ACK
Max-Forwards: 66
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
<--- SIP read from UDP:216.115.69.144:5060 --->
INVITE sip:12012156850@192.168.0.35:5061 SIP/2.0
Record-Route: <sip:216.115.69.144;lr>
Record-Route: <sip:70.167.153.134;lr>
To: <sip:+12012156850@flowroute.com>
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcaa7
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKa2fe.f0e1b08f445d4958e95fc9ef2aa88f6c.0
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bKa2fe.a38358a63c45b107677eff1dc1adf029.1
Via: SIP/2.0/UDP 70.167.153.134;branch=z9hG4bKa2fe.a0c5babf243b198abb72d0db9273ef19.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK04Bf37f42a9b70284bd
Call-ID: 654633502_1873778@4.55.17.35
CSeq: 2304 INVITE
Max-Forwards: 66
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "Unavailable" <sip:Restricted@4.55.17.35:5060>
Content-Length: 222
Content-Type: application/sdp
P-Asserted-Identity: "Unavailable " <sip:UNAVAILABLE@flowroute.com>
v=0
o=- 3767 307 IN IP4 4.55.17.2
s=-
c=IN IP4 4.55.17.2
t=0 0
m=audio 5834 RTP/AVP 0 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:20
<------------->
--- (17 headers 12 lines) ---
Sending to 216.115.69.144:5060 (NAT)
Using INVITE request as basis request - 654633502_1873778@4.55.17.35
Found peer 'flowroute' for 'UNAVAILABLE' from 216.115.69.144:5060
<--- Reliably Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKa2fe.f0e1b08f445d4958e95fc9ef2aa88f6c.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bKa2fe.a38358a63c45b107677eff1dc1adf029.1
Via: SIP/2.0/UDP 70.167.153.134;branch=z9hG4bKa2fe.a0c5babf243b198abb72d0db9273ef19.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK04Bf37f42a9b70284bd
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcaa7
To: <sip:+12012156850@flowroute.com>;tag=as5d76fb6b
Call-ID: 654633502_1873778@4.55.17.35
CSeq: 2304 INVITE
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="277eeaf8"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '654633502_1873778@4.55.17.35' in 32000 ms (Method: INVITE)
<--- SIP read from UDP:216.115.69.144:5060 --->
ACK sip:12012156850@192.168.0.35:5061 SIP/2.0
To: <sip:+12012156850@flowroute.com>;tag=as5d76fb6b
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcaa7
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKa2fe.f0e1b08f445d4958e95fc9ef2aa88f6c.0
Call-ID: 654633502_1873778@4.55.17.35
CSeq: 2304 ACK
Max-Forwards: 66
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
<--- SIP read from UDP:216.115.69.144:5060 --->
INVITE sip:12012156850@192.168.0.35:5061 SIP/2.0
Record-Route: <sip:216.115.69.144;lr>
Record-Route: <sip:216.115.69.132;lr>
To: <sip:+12012156850@flowroute.com>
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK0701caf3
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKe757.09023c1c2c7a364f9ec4336291bafd31.0
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bKe757.1f359809bc31bfa265b4909e84433f1a.1
Via: SIP/2.0/UDP 216.115.69.132;branch=z9hG4bKe757.6b3c1d49eb2de54f3d28a1160a312fa6.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK07B9d036ee80c6409ba
Call-ID: 654772290_71235298@4.55.17.35
CSeq: 29838 INVITE
Max-Forwards: 66
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "Unavailable" <sip:Restricted@4.55.17.35:5060>
Content-Length: 225
Content-Type: application/sdp
P-Asserted-Identity: "Unavailable " <sip:UNAVAILABLE@flowroute.com>
v=0
o=- 16468 6872 IN IP4 4.55.17.2
s=-
c=IN IP4 4.55.17.2
t=0 0
m=audio 20054 RTP/AVP 0 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:20
<------------->
--- (17 headers 12 lines) ---
Sending to 216.115.69.144:5060 (NAT)
Using INVITE request as basis request - 654772290_71235298@4.55.17.35
Found peer 'flowroute' for 'UNAVAILABLE' from 216.115.69.144:5060
<--- Reliably Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKe757.09023c1c2c7a364f9ec4336291bafd31.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bKe757.1f359809bc31bfa265b4909e84433f1a.1
Via: SIP/2.0/UDP 216.115.69.132;branch=z9hG4bKe757.6b3c1d49eb2de54f3d28a1160a312fa6.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK07B9d036ee80c6409ba
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK0701caf3
To: <sip:+12012156850@flowroute.com>;tag=as220236c2
Call-ID: 654772290_71235298@4.55.17.35
CSeq: 29838 INVITE
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="48058949"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '654772290_71235298@4.55.17.35' in 32000 ms (Method: INVITE)
<--- SIP read from UDP:216.115.69.144:5060 --->
ACK sip:12012156850@192.168.0.35:5061 SIP/2.0
To: <sip:+12012156850@flowroute.com>;tag=as220236c2
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK0701caf3
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKe757.09023c1c2c7a364f9ec4336291bafd31.0
Call-ID: 654772290_71235298@4.55.17.35
CSeq: 29838 ACK
Max-Forwards: 66
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
<--- SIP read from UDP:216.115.69.144:5060 --->
INVITE sip:12012156850@192.168.0.35:5061 SIP/2.0
Record-Route: <sip:216.115.69.144;lr>
Record-Route: <sip:70.167.153.134;lr>
To: <sip:+12012156850@flowroute.com>
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcda3
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK3ac2.5dd36f0e6dfa5f28dc8ebd8cadfca4dd.0
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bK3ac2.75d2a33e9aca2bdac9150a860bffd7ff.1
Via: SIP/2.0/UDP 70.167.153.134;branch=z9hG4bK3ac2.8daa36c03c389a67e00f77734eeb517f.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK04Bf38161b2cfa89da4
Call-ID: 654633504_9282606@4.55.17.35
CSeq: 27147 INVITE
Max-Forwards: 66
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "Unavailable" <sip:Restricted@4.55.17.35:5060>
Content-Length: 225
Content-Type: application/sdp
P-Asserted-Identity: "Unavailable " <sip:UNAVAILABLE@flowroute.com>
v=0
o=- 9082 12316 IN IP4 4.55.17.2
s=-
c=IN IP4 4.55.17.2
t=0 0
m=audio 10638 RTP/AVP 0 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:20
<------------->
--- (17 headers 12 lines) ---
Sending to 216.115.69.144:5060 (NAT)
Using INVITE request as basis request - 654633504_9282606@4.55.17.35
Found peer 'flowroute' for 'UNAVAILABLE' from 216.115.69.144:5060
<--- Reliably Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK3ac2.5dd36f0e6dfa5f28dc8ebd8cadfca4dd.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 216.115.69.131;branch=z9hG4bK3ac2.75d2a33e9aca2bdac9150a860bffd7ff.1
Via: SIP/2.0/UDP 70.167.153.134;branch=z9hG4bK3ac2.8daa36c03c389a67e00f77734eeb517f.0
Via: SIP/2.0/UDP 4.55.17.35:5060;branch=z9hG4bK04Bf38161b2cfa89da4
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcda3
To: <sip:+12012156850@flowroute.com>;tag=as0046e47f
Call-ID: 654633504_9282606@4.55.17.35
CSeq: 27147 INVITE
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="19f9dc92"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '654633504_9282606@4.55.17.35' in 32000 ms (Method: INVITE)
<--- SIP read from UDP:216.115.69.144:5060 --->
ACK sip:12012156850@192.168.0.35:5061 SIP/2.0
To: <sip:+12012156850@flowroute.com>;tag=as0046e47f
From: "Unavailable " <sip:UNAVAILABLE@flowroute.com>;tag=gK046dcda3
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK3ac2.5dd36f0e6dfa5f28dc8ebd8cadfca4dd.0
Call-ID: 654633504_9282606@4.55.17.35
CSeq: 27147 ACK
Max-Forwards: 66
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
Really destroying SIP dialog '654451177_22877706@4.55.17.35' Method: ACK
Really destroying SIP dialog '654985977_1582212@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077490_1626186@4.55.17.35' Method: ACK
Really destroying SIP dialog '654451179_76153871@4.55.17.35' Method: ACK
Really destroying SIP dialog '7c14cf24-23172ed3-8a41534@70.167.153.136' Method: OPTIONS
Really destroying SIP dialog '654701164_119225703@4.55.17.35' Method: ACK
Really destroying SIP dialog '654451181_97109371@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077493_129398085@4.55.17.35' Method: ACK
Really destroying SIP dialog '654772271_112523368@4.55.17.35' Method: ACK
Really destroying SIP dialog '655190534_88809733@4.55.17.35' Method: ACK
Really destroying SIP dialog '655233561_6292630@4.55.17.35' Method: ACK
Really destroying SIP dialog '654772276_32518266@4.55.17.35' Method: ACK
Really destroying SIP dialog '654985980_38833135@4.55.17.35' Method: ACK
Really destroying SIP dialog '654701168_19997706@4.55.17.35' Method: ACK
Really destroying SIP dialog '654930032_49281988@4.55.17.35' Method: ACK
Really destroying SIP dialog '654633492_100223044@4.55.17.35' Method: ACK
Really destroying SIP dialog '654772279_118038079@4.55.17.35' Method: ACK
Really destroying SIP dialog '654701170_93565369@4.55.17.35' Method: ACK
Really destroying SIP dialog '654753895_67033442@4.55.17.35' Method: ACK
Really destroying SIP dialog '068e82f6-52c4a995-4ecc765@216.115.69.131' Method: OPTIONS
Really destroying SIP dialog '655077499_56721426@4.55.17.35' Method: ACK
Really destroying SIP dialog '655190536_51147198@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077501_105611257@4.55.17.35' Method: ACK
Really destroying SIP dialog '654451190_250268@4.55.17.35' Method: ACK
Really destroying SIP dialog '654930034_6988078@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077503_50565897@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077504_111759587@4.55.17.35' Method: ACK
Really destroying SIP dialog '654930036_4042503@4.55.17.35' Method: ACK
Really destroying SIP dialog '654772286_8224795@4.55.17.35' Method: ACK
Really destroying SIP dialog '654753902_30767751@4.55.17.35' Method: ACK
Really destroying SIP dialog '655077507_33020797@4.55.17.35' Method: ACK
Really destroying SIP dialog '654633500_30497029@4.55.17.35' Method: ACK
Really destroying SIP dialog '655233566_29683279@4.55.17.35' Method: ACK
Really destroying SIP dialog '654633502_1873778@4.55.17.35' Method: ACK
<--- SIP read from UDP:216.115.69.144:5060 --->
OPTIONS sip:121.135.82.1:1024 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK95af.2b3bf82ab1bd13ee864cc63dc8ec05bb.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received="sip:121.135.82.1:1024">
From: sip:ping@invalid;tag=81c96cf5
To: sip:121.135.82.1:1024
Call-ID: 7c14cf24-bbb72ed3-fd41534@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0
<------------->
--- (11 headers 0 lines) ---
Looking for s in from-sip-external (domain 121.135.82.1:1024)
<--- Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK95af.2b3bf82ab1bd13ee864cc63dc8ec05bb.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=81c96cf5
To: sip:121.135.82.1:1024;tag=as72c2e6dc
Call-ID: 7c14cf24-bbb72ed3-fd41534@70.167.153.136
CSeq: 1 OPTIONS
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:121.135.82.1:5060>
Accept: application/sdp
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '7c14cf24-bbb72ed3-fd41534@70.167.153.136' in 32000 ms (Method: OPTIONS)
Really destroying SIP dialog '654772290_71235298@4.55.17.35' Method: ACK
Really destroying SIP dialog '654633504_9282606@4.55.17.35' Method: ACK
<--- SIP read from UDP:216.115.69.144:5060 --->
OPTIONS sip:121.135.82.1:1024 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK7383.cb999a90d3e07044a62022fa67570436.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received="sip:121.135.82.1:1024">
From: sip:ping@invalid;tag=6cef76a7
To: sip:121.135.82.1:1024
Call-ID: 068e82f6-fa65a995-b1dc765@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0
<------------->
--- (11 headers 0 lines) ---
Looking for s in from-sip-external (domain 121.135.82.1:1024)
<--- Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK7383.cb999a90d3e07044a62022fa67570436.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=6cef76a7
To: sip:121.135.82.1:1024;tag=as650d42f8
Call-ID: 068e82f6-fa65a995-b1dc765@216.115.69.131
CSeq: 1 OPTIONS
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:121.135.82.1:5060>
Accept: application/sdp
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '068e82f6-fa65a995-b1dc765@216.115.69.131' in 32000 ms (Method: OPTIONS)
Reliably Transmitting (NAT) to 192.168.0.138:5062:
OPTIONS sip:1000@192.168.0.138:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.245:5060;branch=z9hG4bK71038112;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.245>;tag=as2e8a4611
To: <sip:1000@192.168.0.138:5062>
Contact: <sip:Unknown@192.168.0.245:5060>
Call-ID: 6a592e1648fc6c0e19c6d9176081caa2@192.168.0.245:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.9.0(1.8.5.0)
Date: Sun, 28 Aug 2011 05:31:49 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
---
<--- SIP read from UDP:192.168.0.138:5062 --->
SIP/2.0 200 OK
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 192.168.0.245:5060;branch=z9hG4bK71038112;rport
From: "Unknown" <sip:Unknown@192.168.0.245>;tag=as2e8a4611
Call-ID: 6a592e1648fc6c0e19c6d9176081caa2@192.168.0.245:5060
To: <sip:1000@192.168.0.138:5062>
Contact: <sip:1000@192.168.0.138:5062>
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
Really destroying SIP dialog '6a592e1648fc6c0e19c6d9176081caa2@192.168.0.245:5060' Method: OPTIONS
Really destroying SIP dialog '7c14cf24-bbb72ed3-fd41534@70.167.153.136' Method: OPTIONS
REGISTER 11 headers, 0 lines
Reliably Transmitting (NAT) to 216.115.69.144:5060:
REGISTER sip:sip.flowroute.com SIP/2.0
Via: SIP/2.0/UDP 121.135.82.1:5060;branch=z9hG4bK494afab4;rport
Max-Forwards: 70
From: <sip:64512793@sip.flowroute.com>;tag=as6fe2e787
To: <sip:64512793@sip.flowroute.com>
Call-ID: 69531dfc31e73c9a34ee19564bd1ba7d@127.0.0.1
CSeq: 112 REGISTER
User-Agent: FPBX-2.9.0(1.8.5.0)
Authorization: Digest username="64512793", realm="sip.flowroute.com", algorithm=MD5, uri="sip:sip.flowroute.com", nonce="TlnTnU5Z0nG45M7iQZ1OFet35Nkc53un", response="2ffd557a00fa54b394e47aa1795c09cb", qop=auth, cnonce="45d5c539", nc=00000002
Expires: 120
Contact: <sip:s@121.135.82.1:5060>
Content-Length: 0
---
<--- SIP read from UDP:216.115.69.144:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 121.135.82.1:5060;branch=z9hG4bK494afab4;rport=1024
From: <sip:64512793@sip.flowroute.com>;tag=as6fe2e787
To: <sip:64512793@sip.flowroute.com>;tag=aa681f9fdf30149b00040f579a1d99c4.092d
Call-ID: 69531dfc31e73c9a34ee19564bd1ba7d@127.0.0.1
CSeq: 112 REGISTER
Contact: <sip:s@192.168.0.35:5061>;q=1;expires=88;received="sip:121.135.82.1:5061", <sip:s@121.135.82.1:5060>;q=1;expires=120;received="sip:121.135.82.1:1024"
Content-Length: 0
<------------->
--- (8 headers 0 lines) ---
Scheduling destruction of SIP dialog '69531dfc31e73c9a34ee19564bd1ba7d@127.0.0.1' in 32000 ms (Method: REGISTER)
Really destroying SIP dialog '068e82f6-fa65a995-b1dc765@216.115.69.131' Method: OPTIONS
<--- SIP read from UDP:216.115.69.144:5060 --->
OPTIONS sip:121.135.82.1:1024 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK2b1e.d172b25dfc92b9f8e594b68abc12a135.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received="sip:121.135.82.1:1024">
From: sip:ping@invalid;tag=796a6cf5
To: sip:121.135.82.1:1024
Call-ID: 7c14cf24-a3682ed3-6151534@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0
<------------->
--- (11 headers 0 lines) ---
Looking for s in from-sip-external (domain 121.135.82.1:1024)
<--- Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK2b1e.d172b25dfc92b9f8e594b68abc12a135.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=796a6cf5
To: sip:121.135.82.1:1024;tag=as256c322e
Call-ID: 7c14cf24-a3682ed3-6151534@70.167.153.136
CSeq: 1 OPTIONS
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:121.135.82.1:5060>
Accept: application/sdp
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '7c14cf24-a3682ed3-6151534@70.167.153.136' in 32000 ms (Method: OPTIONS)
<--- SIP read from UDP:216.115.69.144:5060 --->
OPTIONS sip:121.135.82.1:1024 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKa51e.46e3f74c3c7715130d372f51c4f1657c.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received="sip:121.135.82.1:1024">
From: sip:ping@invalid;tag=849086a7
To: sip:121.135.82.1:1024
Call-ID: 068e82f6-1316a995-25dc765@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0
<------------->
--- (11 headers 0 lines) ---
Looking for s in from-sip-external (domain 121.135.82.1:1024)
<--- Transmitting (NAT) to 216.115.69.144:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKa51e.46e3f74c3c7715130d372f51c4f1657c.0;received=216.115.69.144;rport=5060
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=849086a7
To: sip:121.135.82.1:1024;tag=as10028de2
Call-ID: 068e82f6-1316a995-25dc765@216.115.69.131
CSeq: 1 OPTIONS
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:121.135.82.1:5060>
Accept: application/sdp
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '068e82f6-1316a995-25dc765@216.115.69.131' in 32000 ms (Method: OPTIONS)
Really destroying SIP dialog '69531dfc31e73c9a34ee19564bd1ba7d@127.0.0.1' Method: REGISTER
Reliably Transmitting (NAT) to 192.168.0.138:5062:
OPTIONS sip:1000@192.168.0.138:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.245:5060;branch=z9hG4bK336e67f3;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.0.245>;tag=as559c2287
To: <sip:1000@192.168.0.138:5062>
Contact: <sip:Unknown@192.168.0.245:5060>
Call-ID: 51d44d440fe4650e74d248c82d5158a9@192.168.0.245:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.9.0(1.8.5.0)
Date: Sun, 28 Aug 2011 05:32:49 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
---
<--- SIP read from UDP:192.168.0.138:5062 --->
SIP/2.0 200 OK
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 192.168.0.245:5060;branch=z9hG4bK336e67f3;rport
From: "Unknown" <sip:Unknown@192.168.0.245>;tag=as559c2287
Call-ID: 51d44d440fe4650e74d248c82d5158a9@192.168.0.245:5060
To: <sip:1000@192.168.0.138:5062>
Contact: <sip:1000@192.168.0.138:5062>
Content-Length: 0