22 Mar 20:14:55.131/GLOBAL/ser[32061]: RECEIVED message from 77.42.172.214:5060:
INVITE sip: SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Contact: <sip::5060>
Max-Forwards: 70
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 322
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
22 Mar 20:14:55.132/2929386207@192_168_1_2/ser[32061]: processing INVITE received from 77.42.172.214
22 Mar 20:14:55.133/GLOBAL/ser[32061]: SENDING message to 77.42.172.214:5060:
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060;received=77.42.172.214
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Server: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0
22 Mar 20:14:55.133/GLOBAL/ser[32061]: SENDING message to 91.121.101.126:5061:
INVITE sip::5061 SIP/2.0
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Contact: <sip::5060>
Max-Forwards: 16
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 370
PortaBilling-Notify: NAT
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 77.42.172.214
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=direction:active
a=oldmediaip:192.168.1.2
22 Mar 20:14:55.133/GLOBAL/b2bua: RECEIVED message from 91.121.101.126:5060:
INVITE sip::5061 SIP/2.0
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Contact: <sip::5060>
Max-Forwards: 16
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 370
PortaBilling-Notify: NAT
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 77.42.172.214
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=direction:active
a=oldmediaip:192.168.1.2
22 Mar 20:14:55.141/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Server: Sippy
WWW-Authenticate: Digest realm="91.121.101.126",nonce="817d2ceb6d199384f440950cb674957849c68e2f"
22 Mar 20:14:55.143/GLOBAL/ser[32061]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Server: Sippy
WWW-Authenticate: Digest realm="91.121.101.126",nonce="817d2ceb6d199384f440950cb674957849c68e2f"
22 Mar 20:14:55.143/GLOBAL/ser[32061]: SENDING message to 91.121.101.126:5061:
ACK sip::5061 SIP/2.0
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
From: "41215505668" <sip:>;tag=264167574
Call-ID: 2929386207@192_168_1_2
To: <sip:>
CSeq: 2 ACK
User-Agent: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0
22 Mar 20:14:55.144/GLOBAL/ser[32061]: SENDING message to 77.42.172.214:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 INVITE
Server: Sippy
WWW-Authenticate: Digest realm="91.121.101.126",nonce="817d2ceb6d199384f440950cb674957849c68e2f"
22 Mar 20:14:55.144/GLOBAL/b2bua: RECEIVED message from 91.121.101.126:5060:
ACK sip::5061 SIP/2.0
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK7e9.bc693f9640dc1dc1adac2bab84d1c86c.0
From: "41215505668" <sip:>;tag=264167574
Call-ID: 2929386207@192_168_1_2
To: <sip:>
CSeq: 2 ACK
User-Agent: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0
22 Mar 20:14:55.485/GLOBAL/ser[32061]: RECEIVED message from 77.42.172.214:5060:
ACK sip: SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKd2d23a97508be5c7394dee9328994ae;rport
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 2 ACK
Contact: <sip::5060>
Max-Forwards: 70
User-Agent: C470IP020970000000
Content-Length: 0
22 Mar 20:14:55.594/GLOBAL/ser[32060]: RECEIVED message from 77.42.172.214:5060:
INVITE sip: SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Contact: <sip::5060>
Authorization: Digest username="41215505668", realm="91.121.101.126", uri="sip:", nonce="817d2ceb6d199384f440950cb674957849c68e2f", response="b8db858b3782fb692a7083c94f64d1db"
Max-Forwards: 70
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 322
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
22 Mar 20:14:55.595/2929386207@192_168_1_2/ser[32060]: processing INVITE received from 77.42.172.214
22 Mar 20:14:55.596/GLOBAL/ser[32060]: SENDING message to 77.42.172.214:5060:
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060;received=77.42.172.214
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0
22 Mar 20:14:55.596/GLOBAL/ser[32060]: SENDING message to 91.121.101.126:5061:
INVITE sip::5061 SIP/2.0
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Contact: <sip::5060>
Authorization: Digest username="41215505668", realm="91.121.101.126", uri="sip:", nonce="817d2ceb6d199384f440950cb674957849c68e2f", response="b8db858b3782fb692a7083c94f64d1db"
Max-Forwards: 16
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 370
PortaBilling-Notify: NAT
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 77.42.172.214
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=direction:active
a=oldmediaip:192.168.1.2
22 Mar 20:14:55.596/GLOBAL/b2bua: RECEIVED message from 91.121.101.126:5060:
INVITE sip::5061 SIP/2.0
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
From: "41215505668" <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Contact: <sip::5060>
Authorization: Digest username="41215505668", realm="91.121.101.126", uri="sip:", nonce="817d2ceb6d199384f440950cb674957849c68e2f", response="b8db858b3782fb692a7083c94f64d1db"
Max-Forwards: 16
User-Agent: C470IP020970000000
Supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 370
PortaBilling-Notify: NAT
v=0
o=41215505668 5006 5 IN IP4 192.168.1.2
s=-
c=IN IP4 77.42.172.214
t=0 0
m=audio 5006 RTP/AVP 8 0 96 97 2 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=direction:active
a=oldmediaip:192.168.1.2
22 Mar 20:14:55.605/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
22 Mar 20:14:55.607/2929386207@192_168_1_2/b2bua: sending AAA request:
User-Name = '41215505668'
Digest-Realm = '91.121.101.126'
Digest-Nonce = '817d2ceb6d199384f440950cb674957849c68e2f'
Digest-Method = 'INVITE'
Digest-URI = 'sip:'
Digest-Algorithm = 'MD5'
Digest-User-Name = '41215505668'
Digest-Response = 'b8db858b3782fb692a7083c94f64d1db'
Calling-Station-Id = '41215505668'
Called-Station-Id = '0033427817546'
h323-conf-id = 'EB9A474A B3004C57 54842429 5DDCD938'
call-id = '2929386207@192_168_1_2'
h323-remote-address = '77.42.172.214'
h323-session-protocol = 'sipv2'
h323-ivr-out = 'PortaBilling_Routing:SIP'
h323-ivr-out = 'PortaBilling_AuthMethod:INVITE'
h323-ivr-out = 'PortaBilling_Notify:NAT;rtpp_level=3'
h323-ivr-out = 'PortaBilling_Seed:838650872'
22 Mar 20:14:55.608/GLOBAL/ser[32063]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
22 Mar 20:14:55.827/2929386207@192_168_1_2/b2bua: AAA request accepted, processing response:
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing:@;g-hunt=seq'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: @;g-hunt=skip;expires=300;credit-time=-1;rtpp=1;patience=20'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: ;cli=0041215505668'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: +;cli=+41215505668'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: +;cli=+41215505668'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: +;cli=+41215505668'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Routing: '
h323-billing-model = 'h323-billing-model=0'
Cisco-AVPair = 'h323-ivr-in=Tariff:private'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_CLI:41215505668'
Cisco-AVPair = 'h323-ivr-in=MOH:1'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_CompleteNumber:33427817546'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Auth_CLD:33427817546'
Cisco-AVPair = 'h323-ivr-in=PortaBilling_Auth_Reseller_CLD:33427817546'
h323-return-code = 'h323-return-code=13'
h323-currency = 'h323-currency=CHF'
h323-preferred-lang = 'h323-preferred-lang=en'
22 Mar 20:14:55.940/GLOBAL/rtpproxy[1097]: received command "U 2929386207@192_168_1_2 77.42.172.214 5006 a.144567084;1 b.144567084"
22 Mar 20:14:55.940/GLOBAL/rtpproxy[1097]: new session 2929386207@192_168_1_2, tag a.144567084 medianum 1 requested, type strong
22 Mar 20:14:55.940/2929386207@192_168_1_2/rtpproxy[1097]: new session on a port 47674 created, tag a.144567084
22 Mar 20:14:55.940/2929386207@192_168_1_2/rtpproxy[1097]: pre-filling caller's address with 77.42.172.214:5006
22 Mar 20:14:55.945/GLOBAL/b2bua: SENDING message to 77.59.226.99:5060:
INVITE sip::5060 SIP/2.0
Via: SIP/2.0/UDP 91.121.101.126:5061;branch=z9hG4bKd41f11b6de461db36bd41ae4f3b2632b;rport
Max-Forwards: 70
From: 41215505668 <sip:>;tag=110ceae764ea3abb323261ea8a9c8800
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 200 INVITE
Contact: Anonymous <sip:91.121.101.126:5061>
Expires: 300
User-Agent: Sippy
cisco-GUID: 3952756554-3003141207-1417946153-1574754616
h323-conf-id: 3952756554-3003141207-1417946153-1574754616
Content-Length: 374
Content-Type: application/sdp
v=0
o=Sippy 137205068 0 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47674 RTP/AVP 8 0 96 97 2 18 101
c=IN IP4 91.121.101.126
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:97 AAL2-G726-32/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=direction:active
a=oldmediaip:192.168.1.2
22 Mar 20:14:55.976/GLOBAL/b2bua: RECEIVED message from 77.59.226.99:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 91.121.101.126:5061;branch=z9hG4bKd41f11b6de461db36bd41ae4f3b2632b;rport
From: 41215505668 <sip:>;tag=110ceae764ea3abb323261ea8a9c8800
To: <sip:>
Call-ID: 2929386207@192_168_1_2
CSeq: 200 INVITE
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER
User-Agent: TELES.VoIPGATE 14.0b 906
Content-Length: 0
22 Mar 20:14:57.394/GLOBAL/b2bua: RECEIVED message from 77.59.226.99:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 91.121.101.126:5061;branch=z9hG4bKd41f11b6de461db36bd41ae4f3b2632b;rport
From: 41215505668 <sip:>;tag=110ceae764ea3abb323261ea8a9c8800
To: <sip:>;tag=302329700153675565196815324302
Call-ID: 2929386207@192_168_1_2
CSeq: 200 INVITE
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER
Contact: <sip:>
User-Agent: TELES.VoIPGATE 14.0b 906
Content-Type: application/sdp
Content-Length: 143
v=0
o=- 2067 1 IN IP4 77.59.226.99
s=-
c=IN IP4 77.59.226.99
t=0 0
m=audio 29032 RTP/AVP 8
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:14:57.397/GLOBAL/rtpproxy[1097]: received command "U 2929386207@192_168_1_2 77.59.226.99 29032 b.144567084;1 a.144567084"
22 Mar 20:14:57.397/2929386207@192_168_1_2/rtpproxy[1097]: adding strong flag to existing session, new=1/0/0
22 Mar 20:14:57.397/2929386207@192_168_1_2/rtpproxy[1097]: lookup on ports 47674/47676, session timer restarted
22 Mar 20:14:57.397/2929386207@192_168_1_2/rtpproxy[1097]: pre-filling callee's address with 77.59.226.99:29032
22 Mar 20:14:57.399/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Content-Length: 149
Content-Type: application/sdp
v=0
o=- 14456708 1 IN IP4 77.59.226.99
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:14:57.400/GLOBAL/ser[32061]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Content-Length: 149
Content-Type: application/sdp
v=0
o=- 14456708 1 IN IP4 77.59.226.99
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:14:57.400/GLOBAL/ser[32061]: SENDING message to 77.42.172.214:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Content-Length: 149
Content-Type: application/sdp
v=0
o=- 14456708 1 IN IP4 77.59.226.99
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:14:57.698/2929386207@192_168_1_2/rtpproxy[1097]: caller's address filled in: 77.42.172.214:1024 (RTP)
22 Mar 20:15:06.856/GLOBAL/b2bua: RECEIVED message from 77.59.226.99:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126:5061;branch=z9hG4bKd41f11b6de461db36bd41ae4f3b2632b;rport
From: 41215505668 <sip:>;tag=110ceae764ea3abb323261ea8a9c8800
To: <sip:>;tag=302329700153675565196815324302
Call-ID: 2929386207@192_168_1_2
CSeq: 200 INVITE
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,REGISTER,PRACK,INFO,NOTIFY,REFER
Contact: <sip:>
User-Agent: TELES.VoIPGATE 14.0b 906
Content-Type: application/sdp
Content-Length: 143
v=0
o=- 2067 1 IN IP4 77.59.226.99
s=-
c=IN IP4 77.59.226.99
t=0 0
m=audio 29032 RTP/AVP 8
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:06.859/GLOBAL/b2bua: SENDING message to 77.59.226.99:5060:
ACK sip: SIP/2.0
Via: SIP/2.0/UDP 91.121.101.126:5061;rport;branch=z9hG4bK661a8e5bd0dfd35597d37800f6594f49
Max-Forwards: 70
From: 41215505668 <sip:>;tag=110ceae764ea3abb323261ea8a9c8800
To: <sip:>;tag=302329700153675565196815324302
Call-ID: 2929386207@192_168_1_2
CSeq: 200 ACK
Expires: 300
User-Agent: Sippy
22 Mar 20:15:06.861/2929386207@192_168_1_2/b2bua: sending Acct Start (Originate):
h323-call-origin = 'originate'
h323-call-type = 'VoIP'
h323-session-protocol = 'sipv2'
h323-setup-time = '19:14:55.930 GMT Sun Mar 22 2009'
User-Name = '41215505668'
Calling-Station-Id = '41215505668'
Called-Station-Id = '0033427817546'
h323-conf-id = 'EB9A474A B3004C57 54842429 5DDCD938'
call-id = '2929386207@192_168_1_2'
Acct-Session-Id = '2929386207@192_168_1_2'
h323-remote-address = '77.59.226.99'
h323-ivr-out = 'DURATION:7200'
h323-ivr-out = 'PortaBilling_Auth_CLD:33427817546'
h323-ivr-out = 'PortaBilling_Seed:838650872'
h323-connect-time = '19:15:06.860 GMT Sun Mar 22 2009'
alert-timepoint = '19:14:57.396 GMT Sun Mar 22 2009'
Acct-Status-Type = 'Start'
22 Mar 20:15:06.863/GLOBAL/rtpproxy[1097]: received command "U 2929386207@192_168_1_2 77.59.226.99 29032 b.144567084;1 a.144567084"
22 Mar 20:15:06.863/2929386207@192_168_1_2/rtpproxy[1097]: adding strong flag to existing session, new=1/0/0
22 Mar 20:15:06.863/2929386207@192_168_1_2/rtpproxy[1097]: lookup on ports 47674/47676, session timer restarted
22 Mar 20:15:06.866/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:06.866/2929386207@192_168_1_2/b2bua: sending Acct Start (Answer):
h323-call-origin = 'answer'
h323-call-type = 'VoIP'
h323-session-protocol = 'sipv2'
h323-setup-time = '19:14:55.828 GMT Sun Mar 22 2009'
User-Name = '41215505668'
Calling-Station-Id = '41215505668'
Called-Station-Id = '0033427817546'
h323-conf-id = 'EB9A474A B3004C57 54842429 5DDCD938'
call-id = '2929386207@192_168_1_2'
Acct-Session-Id = '2929386207@192_168_1_2'
h323-remote-address = '77.42.172.214'
h323-ivr-out = 'PortaBilling_Seed:838650872'
h323-connect-time = '19:15:06.866 GMT Sun Mar 22 2009'
alert-timepoint = '19:15:06.866 GMT Sun Mar 22 2009'
Acct-Status-Type = 'Start'
22 Mar 20:15:06.868/GLOBAL/ser[32063]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:06.868/GLOBAL/ser[32063]: SENDING message to 77.42.172.214:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:07.401/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:07.403/GLOBAL/ser[32060]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:07.403/GLOBAL/ser[32060]: SENDING message to 77.42.172.214:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:08.411/GLOBAL/b2bua: SENDING message to 91.121.101.126:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:08.412/GLOBAL/ser[32062]: RECEIVED message from 91.121.101.126:5061:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.101.126;branch=z9hG4bK8e9.08a209d6a0e663ca960ddd99d89f6f12.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=77.42.172.214;branch=z9hG4bK34823c727f4fc5effeabde7f6943ecd;rport=5060
Record-Route: <sip:91.121.101.126;ftag=264167574;lr>
From: 41215505668 <sip:>;tag=264167574
To: <sip:>;tag=f518b3d339c946b67818d0c4384f1405
Call-ID: 2929386207@192_168_1_2
CSeq: 3 INVITE
Server: Sippy
Contact: Anonymous <sip:91.121.101.126:5061>
Content-Length: 156
Content-Type: application/sdp
v=0
o=Sippy 142488268 1 IN IP4 91.121.101.126
s=-
t=0 0
m=audio 47676 RTP/AVP 8
c=IN IP4 91.121.101.126
a=sendrecv
a=ptime:10
a=rtpmap:8 PCMA/8000
22 Mar 20:15:08.412/GLOBAL/ser[32062]: SENDING message to 77.42.172.214:5060: