7 May
2015
7 May
'15
11:59 a.m.
Hello;
i am trying to understand how is ims_charging working . Kamailio is
a S-CSCF here. kamailio and call dont have a problem but ro_session.
i always get ro_session_ontimeout() ERROR. when look diameter trace
, ims_charging module dont request for 30 more sec for granted and kill
dialog.
Thanks for helps.
14:22:51 S-CSCF ----->CC-Time 15 .. Sec CCR ---> Java-Diamaeter
Server (INITIAL REQ)
14:22:51 S-CSCF <-----CC-Time 15 .. Sec CCA <--- Java-Diamaeter
Server (INITIAL REQ)
14:23:01 S-CSCF ----->CC-Time 10 .. Sec CCR ---> Java-Diamaeter
Server (UPDATE )
14:23:01 S-CSCF <-----CC-Time 30 .. Sec CCA <--- Java-Diamaeter
Server (UPDATE )
14:23:31 S-CSCF ----->CC-Time 30 .. Sec CCR ---> Java-Diamaeter
Server (TERMINATE )
14:23:31 S-CSCF <-----CC-Time 30 .. Sec CCA <--- Java-Diamaeter
Server (TERMINATE )
------ LOG -----
May 7 14:23:31 /usr/local/sbin/kamailio[7602]: ERROR: ims_charging
[ro_timer.c:449]: ro_session_ontimeout(): Diameter call session - event [2]
May 7 14:23:31 /usr/local/sbin/kamailio[7602]: INFO: ims_charging
[ro_timer.c:452]: ro_session_ontimeout(): Call/session must be ended -
no more funds.
May 7 14:23:31 /usr/local/sbin/kamailio[7600]: WARNING: ims_charging
[dialog.c:167]: dlg_terminated(): inconsistent ro timer data on
ro_session 0x7ff1eb4543b8 []
---- CFG ------
$var(cc_ret) = Ro_CCR("CHARGING_CCR_REPLY", "orig", "SCUR",
"", "15",
"location");
---- CFG ------