New subject: to tag not correctly inserted in rtpproxy command with kamailio 3.2.2

21 Mar 2012

Dear all,

I see that in some scenario the To Tag is not passed in the command string
to configure the rtpproxy.

At least I see this scenario:

I start a call -> all is ok

I do a ReINVITE without any SDP in the INVITE , so I call the rtp_offer()
for the 200 OK and the function rtpproxy_answer() for the ACK

The problem is with the function rtpproxy_answer() only the from tag is
passed so the stream cannot be found (lookup request failed) 

I do a test with the version 3.2.1 and they was no problem. Bellow rtpproxy
log of both version. 

Regards

Laurent

With ver: 3.2.2

Mar 21 16:03:46 proxy3 rtpproxy[22197]: DBUG:handle_command: received
command "24732_28 Uc0,8,18,101 ec1cdd343243785b663cc52b5af08cf0(a)50.10.21.92
62.12.250.165 62968 pm04tutcvv;1 1332342221131;1"

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: adding strong
flag to existing session, new=1/0/0

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: lookup on ports
11416/18748, session timer restarted

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: update

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command:   update from
cmd requested

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: new IP :
62.12.250.165's address port 62968

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: old IP:
62.12.250.165 address port 26495

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command:  RTP IP are the
same, we don't update them

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command:  RTCP IP are
the same, we don't update them

Mar 21 16:03:46 proxy3 rtpproxy[22197]: DBUG:doreply: sending reply
"24732_28 18748 50.10.21.8#012"

Mar 21 16:03:46 proxy3 rtpproxy[22197]: DBUG:handle_command: received
command "24679_17 Lc0,101 ec1cdd343243785b663cc52b5af08cf0(a)50.10.21.92
50.10.21.92 64078 pm04tutcvv;1"

Mar 21 16:03:46 proxy3 rtpproxy[22197]: INFO:handle_command: lookup request
failed: session ec1cdd343243785b663cc52b5af08cf0(a)50.10.21.92, tags
pm04tutcvv;1/NONE not found

Mar 21 16:03:46 proxy3 rtpproxy[22197]: DBUG:doreply: sending reply
"24679_17 0 50.10.21.8#012"

With ver: 3.2.1

Mar 21 18:18:04 proxy3 rtpproxy[22197]: DBUG:handle_command: received
command "10958_13 Uc0,8,18,101 4e21d3a85ce70fe0dfa28f517484cba1(a)50.10.21.92
62.12.250.165 56522 jddmr2qwrf;1 1332350278581;1"

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: adding strong
flag to existing session, new=1/0/0

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: lookup on ports
9974/16864, session timer restarted

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: update

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command:   update from
cmd requested

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: new IP :
62.12.250.165's address port 56522

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: old IP:
62.12.250.165 address port 29436

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command:  RTP IP are the
same, we don't update them

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command:  RTCP IP are
the same, we don't update them

Mar 21 18:18:04 proxy3 rtpproxy[22197]: DBUG:doreply: sending reply
"10958_13 16864 50.10.21.8#012"

Mar 21 18:18:04 proxy3 rtpproxy[22197]: DBUG:handle_command: received
command "10793_9 Lc0,101 4e21d3a85ce70fe0dfa28f517484cba1(a)50.10.21.92
50.10.21.92 63990 jddmr2qwrf;1 1332350278581;1"

Mar 21 18:18:04 proxy3 rtpproxy[22197]: INFO:handle_command: lookup on ports
9974/16864, session timer restarted