[OpenSIPS-Users] diiference between 1.6.1 and 1.6.2
erik pepermans
cpu1 at telenet.be
Tue Mar 23 20:36:15 CET 2010
Hi Bogdan,
Sorry - I actually meant there are no mediatrace records in the
media_sessions table of mediaproxy instead of siptrace records in the
sip_trace table of opensips.
Brgds
Erik
-----Oorspronkelijk bericht-----
Van: users-bounces at lists.opensips.org
[mailto:users-bounces at lists.opensips.org] Namens Bogdan-Andrei Iancu
Verzonden: dinsdag 23 maart 2010 10:42
Aan: OpenSIPS users mailling list
Onderwerp: Re: [OpenSIPS-Users] diiference between 1.6.1 and 1.6.2
Hi Erik,
according the logs, the siptrace is inserting some records in the DB
(what you posted is for inserting a reply record). Are you sure you
don't get the data in DB ??
Regards,
Bogdan
erik pepermans wrote:
> Hi Bogdan,
>
> What I can see is :
>
> Afer invite :
>
> Mar 22 22:38:02 [2889] DBG:siptrace:trace_onreply_out: dest
> [udp:77.xx.xx.xx:5060] Mar 22 22:38:02 [2889]
> DBG:siptrace:trace_onreply_out: storing info... Mar 22 22:38:02 [2889]
> DBG:db_mysql:has_stmt_ctx: ctx found for sip_trace
>
> ...
>
> Mar 22 22:38:02 [2889] DBG:dialog:dlg_onroute: Route param 'did' not
> found
>
> Has the above something to do with it ?
>
> The script itself is fairly simple :
>
> ...
> loadmodule "db_mysql.so"
> loadmodule "signaling.so"
> loadmodule "sl.so"
> loadmodule "tm.so"
> loadmodule "rr.so"
> loadmodule "maxfwd.so"
> loadmodule "usrloc.so"
> loadmodule "registrar.so"
> loadmodule "textops.so"
> loadmodule "mi_fifo.so"
> loadmodule "mi_datagram.so"
> loadmodule "uri.so"
> loadmodule "xlog.so"
> loadmodule "acc.so"
> loadmodule "drouting.so"
> loadmodule "dialog.so"
> loadmodule "aaa_radius.so"
> loadmodule "alias_db.so"
> loadmodule "siptrace.so"
> loadmodule "mediaproxy.so"
> loadmodule "perl.so"
> ...
> # ----- siptrace params -----
> modparam("siptrace", "db_url",
> "mysql://user:pass@foo.bar/user") modparam("siptrace",
> "trace_flag", 22) modparam("siptrace", "trace_on", 1)
> ...
> ####### Routing Logic ########
>
> # main request routing logic
>
> route{
>
> if (!mf_process_maxfwd_header("10")) {
> sl_send_reply("483","Too Many Hops");
> exit;
> }
>
> force_rport();
>
> setflag(22);
> ...
> route[1] {
> # for INVITEs enable some additional helper routes
> if (is_method("INVITE")) {
> t_on_branch("2");
> t_on_reply("2");
> t_on_failure("1");
> }
>
> sip_trace();
>
>
> rewritehostport("77.yy.yy.yy:5060");
>
> if (!t_relay()) {
> sl_reply_error();
> };
> acc_aaa_request("aaa_extra");
> exit;
> }
>
> Hopes this helps a bit
>
> Brgds
> Erik
>
> -----Oorspronkelijk bericht-----
> Van: users-bounces at lists.opensips.org
> [mailto:users-bounces at lists.opensips.org] Namens Bogdan-Andrei Iancu
> Verzonden: zondag 21 maart 2010 23:30
> Aan: OpenSIPS users mailling list
> Onderwerp: Re: [OpenSIPS-Users] diiference between 1.6.1 and 1.6.2
>
>
> Hi Erik,
>
> for the siptrace part,how are you triggering the tracing in the script
> ?
> Also, if possible,can you enable debug=6 and post the logs related to
> INVITE siptracing?
>
> Regards,
> Bogdan
>
> erik pepermans wrote:
>
>> Hi,
>>
>> Using version 1.6.1-notls with mediaproxy module, the increments of
>> KBIn and KBOut in CDRTool work OK; this has stopped in 1.6.2-notls.
>> Moreover the siptrace module doesn't return any record anymore in the
>> siptrace table as of 1.6.2.
>>
>> The opensips.cfg is exactly the same I used in both versions.
>>
>> Brgds
>> Erik
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
>> and is believed to be clean.
>> ---------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
>
--
Bogdan-Andrei Iancu
www.voice-system.ro
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the Users
mailing list