Hi Daniel,
debbuger module does not come handy, in fact it told me that yes rtpproxy_manage is
executed two times in a raw (look at the xlog tag AFTER RTPPROXY_MANAGE)
rtpproxy[16]: DBUG:GLOBAL:rtpc_doreply: sending reply "1\n"
{1 2 INVITE 79961MDUxZmM4YWEyNThlMjUxM2FkNTA3M2Q3NWYwNTZjZTk} 8(30) INFO: <script>:
[4001@OUTGOINGPUBLIC:57704]{INVITE} From Outside World to Asterisk Box
sip:10.20.69.3:5080
{1 102 NOTIFY 3d285c502fe9d50d37ea785b1fff027e@PUBLICIP} 5(27) INFO: <script>:
[4001@10.20.69.3:5080]{NOTIFY} AFTER RTPPROXY_MANAGE Call from Media-Server Cluster
{1 102 NOTIFY 33380a015a51d35f1c6e9eb72d6333dc@PUBLICIP} 7(29) INFO: <script>:
[4005@10.20.69.3:5080]{NOTIFY} AFTER RTPPROXY_MANAGE Call from Media-Server Cluster
rtpproxy[16]: DBUG:GLOBAL:get_command: received command "30_8 UASEIc0,8,3,101
463ddcb0678b788b780821b7501c4dc8@PUBLICIP 10.20.69.3 12556 as3c837952;1"
rtpproxy[16]: INFO:GLOBAL:rtpp_command_ul_handle: new IPv4/IPv4 session
463ddcb0678b788b780821b7501c4dc8@PUBLICIP, tag as3c837952;1 requested, type strong
rtpproxy[16]: INFO:463ddcb0678b788b780821b7501c4dc8@PUBLICIP:rtpp_command_ul_handle: new
session on IPv4 port 57116 created, tag as3c837952;1
rtpproxy[16]: INFO:463ddcb0678b788b780821b7501c4dc8@PUBLICIP:rtpp_stream_prefill_addr:
pre-filling caller's RTP address with 10.20.69.3:12556
rtpproxy[16]: INFO:463ddcb0678b788b780821b7501c4dc8@PUBLICIP:rtpp_stream_prefill_addr:
pre-filling caller's RTCP address with 10.20.69.3:12557
rtpproxy[16]: DBUG:GLOBAL:rtpc_doreply: sending reply "57116 PUBLICIP\n"
{1 102 INVITE 463ddcb0678b788b780821b7501c4dc8@PUBLICIP} 8(30) INFO: <script>:
[4005@10.20.69.3:5080]{INVITE} AFTER RTPPROXY_MANAGE Call from Media-Server Cluster
rtpproxy[16]: DBUG:GLOBAL:get_command: received command "30_9 UASEIc0,8,3,101
463ddcb0678b788b780821b7501c4dc8@PUBLICIP 10.20.69.3 12556 as3c837952;1"
{1 102 INVITE 463ddcb0678b788b780821b7501c4dc8@PUBLICIP} 8(30) INFO: <script>:
[4005@10.20.69.3:5080]{INVITE} AFTER RTPPROXY_MANAGE Call from Media-Server Cluster
rtpproxy[16]: INFO:463ddcb0678b788b780821b7501c4dc8@PUBLICIP:rtpp_command_ul_handle:
adding strong flag to existing session, new=1/0/0
rtpproxy[16]: INFO:463ddcb0678b788b780821b7501c4dc8@PUBLICIP:rtpp_command_ul_handle:
lookup on ports 57116/0, session timer restarted
rtpproxy[16]: DBUG:GLOBAL:rtpc_doreply: sending reply "57116 PUBLICIP\n"
Does log_prefix permit to go deeper in debug ?
Above is not relevant-enough to highlight a strange sdp body.
----- Mail original -----
De: "Daniel-Constantin Mierla" <miconda(a)gmail.com>
À: "Sébastien Brice" <sebastien.brice(a)jvs.fr>fr>, "sr-users"
<sr-users(a)lists.sip-router.org>
Envoyé: Jeudi 16 Juin 2016 08:15:13
Objet: Re: [SR-Users] just a quick glance at my kamailio.cfg (suspect a rtpproxy_manage
behavior)
Hello,
didn't get the chance to look at config yet, but I want to suggest using
debugger module with cfgtrace enabled, eventually with log_prefix from
core printing the callid and method. The you can see what actions from
kamailio.cfg are executed and in that way be sure that rtpproxy
functions are not executed two times.
Cheers,
Daniel
On 15/06/16 23:28, Sébastien Brice wrote:
Hi guys
i am bridging call on a private ip asterisk behind kamailio/rtpproxy
i am calling rtpproxy with the route [FROMASTERISK]
route[FROMASTERISK] {
if(ds_is_from_list()){
xlog("L_INFO","$dd Call from Media-Server Cluster\n");
rtpproxy_manage("cawei");
SIP INVITE with sdp always report a corrupt body!!!
Session Name (s): Asterisk PBX 13.9.1
Connection Information (c): IN IP4 PUBLICIPPUBLICIP
Connection Address: PUBLICIPPUBLICIP
thats really strange since i am calling rtpproxy_manage only once i can't understand
it appears twice.
what do you think about that ? thx you
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com -
http://www.kamailio.org
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda