[Serusers] Mediaproxy problem

Mon Nov 8 22:36:24 CET 2004

Hello List.
	Thanks for the answers about my last question.   Now i have another
problem.  I installed mediaproxy to work with some NAT'd clients.   When a
NAT'd client calls to another client i only have voice in one way.  This, at
first sight, seems to be a configuration problem, but i'm using the same
configuration that in my lab test and worked ok.  So i'm a little bit
confused about this situation.  For the other hand the only thing added in
this new configuration is a "exec" command that changes the R-URI for all
the calls (add a prefix).  I'm attaching part of the debug of the call and
part of the debug of the mediaproxy (tail -f /var/log/messages).

#
U xx.xx.148.186:64443 -> xx.xx.154.35:5060
  INVITE sip:2408196 at sipproxy.mydomain.com SIP/2.0
Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bKc0420a0ba45
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 5 INVITE
Supported: timer, replaces
Min-SE: 1800
Date: Tue, 14 Jun 2005 02:15:28 GMT
User-Agent: AddPac SIP Gateway
Contact: <sip:5555848110 at 192.168.0.191>
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, REFER, NOTIFY
Content-Type: application/sdp
Content-Length: 241
Max-Forwards: 70

v=0
o=5555848110 1118715328 1118715328 IN IP4 192.168.0.191
s=AddPac Gateway SDP
c=IN IP4 192.168.0.191
t=1118715328 0
m=audio 23006 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

#
U xx.xx.154.35:5060 -> xx.xx.148.186:64443
  SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
192.168.0.191:5060;branch=z9hG4bKc0420a0ba45;rport=64443;received=xx.xx.148.
186
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To:
<sip:2408196 at sipproxy.mydomain.com>;tag=6eb14299de2cc731d173c135064daec5.695
6
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 5 INVITE
Proxy-Authenticate:Digest realm="sipproxy.mydomain.com",
nonce="418faa143a3b169ae45516c762eb6effa17fa462", qop="auth"
Server: Sip EXpress router(0.8.14-3 (i386/linux))
Content-Length: 0
Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells:  pid=12040
req_src_ip=xx.xx.148.186 req_src_port=64443
in_uri=sip:2408196 at sipproxy.mydomain.com
out_uri=sip:7072408196 at sipproxy.mydomain.com via_cnt==1"
.
  .

#
U xx.xx.148.186:64443 -> xx.xx.154.35:5060
  ACK sip:2408196 at sipproxy.mydomain.com SIP/2.0
Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bKc0420a0ba45
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To:
<sip:2408196 at sipproxy.mydomain.com>;tag=6eb14299de2cc731d173c135064daec5.695
6
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 5 ACK
Content-Length: 0
Max-Forwards: 70

#
U xx.xx.148.186:64443 -> xx.xx.154.35:5060
  INVITE sip:2408196 at sipproxy.mydomain.com SIP/2.0
Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bKc0420a0ba46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
Supported: timer, replaces
Min-SE: 1800
Date: Tue, 14 Jun 2005 02:15:28 GMT
User-Agent: AddPac SIP Gateway
Contact: <sip:5555848110 at 192.168.0.191>
Accept: application/sdp
Proxy-Authorization: Digest username="1-12-2MPK8X2PK2",
realm="sipproxy.mydomain.com",
nonce="418faa143a3b169ae45516c762eb6effa17fa462",
uri="sip:2408196 at sipproxy.mydomain.com", qop=auth, nc=00000001,
cnonce="c651d599", response="9f78e67834ea62cf90682f60b4aa7191",
algorithm=MD5
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, REFER, NOTIFY
Content-Type: application/sdp
Content-Length: 241
Max-Forwards: 70

v=0

o=5555848110 1118715328 1118715328 IN IP4 192.168.0.191
s=AddPac Gateway SDP
c=IN IP4 192.168.0.191
t=1118715328 0
m=audio 23006 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

#
U xx.xx.154.35:5060 -> xx.xx.148.186:64443
  SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP
192.168.0.191:5060;branch=z9hG4bKc0420a0ba46;rport=64443;received=xx.xx.148.
186
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
Server: Sip EXpress router (0.8.14-3 (i386/linux))
Content-Length: 0
Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells:  pid=12037
req_src_ip=xx.xx.148.186
req_src_port=64443in_uri=sip:2408196 at sipproxy.mydomain.com
out_uri=sip:7072408196 at xx.xx.148.231:5060 via_cnt==1"

#
U xx.xx.154.35:5060 -> xx.xx.148.231:5060
  INVITE sip:7072408196 at xx.xx.148.231:5060 SIP/2.0
Record-Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKcc3.a0569a31.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
Supported: timer, replaces
Min-SE: 1800
Date: Tue, 14 Jun 2005 02:15:28 GMT
User-Agent: AddPac SIP Gateway
Contact: <sip:5555848110 at xx.xx.148.186:64443>
Accept: application/sdp
Proxy-Authorization: Digest username="1-12-2MPK8X2PK2",
realm="sipproxy.mydomain.com",
nonce="418faa143a3b169ae45516c762eb6effa17fa462",
uri="sip:2408196 at sipproxy.mydomain.com", qop=auth, nc=00000001,
cnonce="c651d599", response="9f78e67834ea62cf90682f60b4aa7191",
algorithm=MD5
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, REFER, NOTIFY
Content-Type: application/sdp
Content-Length: 240
Max-Forwards: 69
P-hint: fixed NAT contact for request
P-hint: H323-Side

v=0
o=5555848110 1118715328 1118715328 IN IP4 192.168.0.191
s=AddPac Gateway SDP
c=IN IP4 xx.xx.154.35
t=1118715328 0
m=audio 35024 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

#
U xx.xx.148.231:5060 -> xx.xx.154.35:5060
  SIP/2.0 100 Trying
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKcc3.a0569a31.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Content-Length: 0

Nov  8 12:12:08 sipvoiss mediaproxy[10717]: command request
c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191 192.168.0.191:23006:audio
xx.xx.148.186 sipproxy.mydomain.com remote sipproxy.mydomain.com remote
AddPac=20SIP=20Gateway
info=from:5555848110 at sipproxy.mydomain.com,to:2408196 at sipproxy.mydomain.com,
fromtag:c0420a0ba4,totag:
Nov  8 12:12:08 sipvoiss mediaproxy[10717]: session
c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191: started. listening on
xx.xx.154.35:35024
Nov  8 12:12:08 sipvoiss mediaproxy[10717]: command execution time:  1.68 ms
#
U xx.xx.148.231:5060 -> xx.xx.154.35:5060
  SIP/2.0 180 Ringing
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKcc3.a0569a31.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Contact: sip:7072408196 at xx.xx.148.231
Content-Length: 0
Record-Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

#
U xx.xx.154.35:5060 -> xx.xx.148.186:64443
  SIP/2.0 180 Ringing
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Contact: sip:7072408196 at xx.xx.148.231
Content-Length: 0
Record-Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

Nov  8 12:12:10 sipvoiss mediaproxy[10717]: session
c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191: 0/0/0 packets, 0/0/0
bytes (caller/called/relayed)
Nov  8 12:12:10 sipvoiss mediaproxy[10717]: session
c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191: ended (did timeout).

#
U xx.xx.148.231:5060 -> xx.xx.154.35:5060
  SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKcc3.a0569a31.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Contact: sip:7072408196 at xx.xx.148.231
Content-Type: application/sdp
Content-Length: 208
Record-Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

v=0
o=7072408196 1099959234 1099959234 IN IP4 xx.xx.148.231
s=AddPac Gateway SDP
c=IN IP4 xx.xx.148.231
t=1099959234 0
m=audio 23300 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15

#
U xx.xx.154.35:5060 -> xx.xx.148.186:64443
  SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 INVITE
User-Agent: AddPac SIP Gateway
Contact: sip:7072408196 at xx.xx.148.231
Content-Type: application/sdp
Content-Length: 208
Record-Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

v=0
o=7072408196 1099959234 1099959234 IN IP4 xx.xx.148.231
s=AddPac Gateway SDP
c=IN IP4 xx.xx.148.231
t=1099959234 0
m=audio 23300 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15

#
U xx.xx.148.186:64443 -> xx.xx.154.35:5060
  ACK sip:7072408196 at xx.xx.148.231 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bKc0420a0ba46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 ACK
Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>
Content-Length: 0
Max-Forwards: 70

#
U xx.xx.154.35:5060 -> xx.xx.148.231:5060
  ACK sip:7072408196 at xx.xx.148.231 SIP/2.0
Record-Route: <sip:7072408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>
Via: SIP/2.0/UDP xx.xx.154.35;branch=0
Via: SIP/2.0/UDP
192.168.0.191:5060;received=xx.xx.148.186;branch=z9hG4bKc0420a0ba46
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 6 ACK
Content-Length: 0
Max-Forwards: 69
P-hint: USRLOC

Nov  8 12:12:19 sipvoiss mediaproxy[10717]: command lookup
c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191 xx.xx.148.231:23300:audio
xx.xx.148.231 sipproxy.mydomain.com remote sipproxy.mydomain.com unknown
AddPac=20SIP=20Gateway
info=from:5555848110 at sipproxy.mydomain.com,to:2408196 at sipproxy.mydomain.com,
fromtag:c0420a0ba4,totag:b741e2b9a4
Nov  8 12:12:19 sipvoiss mediaproxy[10717]: warning: trying to lookup
session with non-existent id:
'c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191'
Nov  8 12:12:19 sipvoiss mediaproxy[10717]: command execution time:  0.25 ms

#
U xx.xx.148.186:64443 -> xx.xx.154.35:5060
  BYE sip:7072408196 at xx.xx.148.231 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bKc0420a0ba47
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 7 BYE
Route: <sip:2408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>
Date: Tue, 14 Jun 2005 02:15:49 GMT
User-Agent: AddPac SIP Gateway
Contact: <sip:5555848110 at 192.168.0.191>
Content-Length: 0
Max-Forwards: 70

#
U xx.xx.154.35:5060 -> xx.xx.148.231:5060
  BYE sip:7072408196 at xx.xx.148.231 SIP/2.0
Record-Route: <sip:7072408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKdc3.ee3b7823.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a47
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 7 BYE
Date: Tue, 14 Jun 2005 02:15:49 GMT
User-Agent: AddPac SIP Gateway
Contact: <sip:5555848110 at xx.xx.148.186:64443>
Content-Length: 0
Max-Forwards: 69
P-hint: fixed NAT contact for request
P-hint: USRLOC

#
U xx.xx.148.231:5060 -> xx.xx.154.35:5060
  SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKdc3.ee3b7823.0
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a47
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 7 BYE
User-Agent: AddPac SIP Gateway
Content-Length: 0
Record-Route: <sip:7072408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

#
U xx.xx.154.35:5060 -> xx.xx.148.186:64443
  SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.0.191:5060;rport=64443;received=xx.xx.148.186;branch=z9hG4bKc0420a0b
a47
From: <sip:5555848110 at sipproxy.mydomain.com>;tag=c0420a0ba4
To: <sip:2408196 at sipproxy.mydomain.com>;tag=b741e2b9a4
Call-ID: c03dae42-d936-0aa2-800b-0002a400f1e9 at 192.168.0.191
CSeq: 7 BYE
User-Agent: AddPac SIP Gateway
Content-Length: 0
Record-Route: <sip:7072408196 at xx.xx.154.35;ftag=c0420a0ba4;lr=on>

As you can see the mediaproxy session is ended by timeout.  I don't
understand why.
Can someone give me a hand here?

Thanks in advance

Ricardo Martinez Ogalde.-