RateEngine problem

renatofb · **Posted:** Wed Oct 06, 2010 11:41 pm

it just happened a strange problem
Everything was working for 6 months now.
all the sudden RateEngine reported it did not match the rate for a call
All rate tables are standard country code then subscriber number.

it happens that for some destination, speacially US, it will give the message below.

Code:

[2010-10-06 20:12:39] WARNING[3845]: chan_sip.c:23246 set_insecure_flags: Unknown insecure mode 'very' on line 0
    -- Executing [1201..<mascarated by me>...@a2billing:1] Ringing("SIP/123456-0000002a", "") in new stack
    -- Executing [1201..<mascarated by me>...@a2billing:2] DeadAGI("SIP/123456-0000002a", "a2billing.php,1") in new stack
[2010-10-06 20:12:39] WARNING[5237]: res_agi.c:3311 deadagi_exec: DeadAGI has been deprecated, please use AGI in all cases!
    -- Launched AGI Script /var/lib/asterisk/agi-bin/a2billing.php
 a2billing.php,1: file:Class.A2Billing.php - line:1006 - uniqueid:1286406759.42 - ERROR ::> RateEngine didnt succeed to match the dialed number over the ratecard (Please check : id the ratecard is well create ; if the removeInter_Prefix is set according to your prefix in the ratecard ; if you hooked the ratecard to the Call Plan)
    -- <SIP/123456-0000002a>AGI Script a2billing.php completed, returning -1
    -- Executing [h@a2billing:1] Hangup("SIP/123456-0000002a", "") in new stack
  == Spawn extension (a2billing, h, 1) exited non-zero on 'SIP/1234563-0000002a'

I can say it was working and nothing has changed.
If I insert 00 in the in the simulator it will match, but again I have no rate initiating with 00
Anyone experienced that and can share your comments how to solve it?

jroper · **Joined:** Fri Jun 23, 2006 3:56 pm **Posts:** 4065

Hi

Check which international prefixes you are removing in the agi-conf, particularly make sure you are not removing the "1"

Joe

renatofb · **Posted:** Sat Oct 09, 2010 7:20 pm

Hi Joe, thanks for your answer,

I checked that and I am removing only 00 and not 011

weird thing is that if country code is not starting with 1 all worked.

just to remind it was all the sudden, it was working.

Could this mean a bug?

jroper · **Joined:** Fri Jun 23, 2006 3:56 pm **Posts:** 4065

Hi

It is unlikely to be a bug as it worked before - something has changed somewhere. I actually asked whether you were removing a 1, not a 011 in the agi-conf, as this would possibly cause the symptoms you describe.

What have you changed to break it, would be first question.

You need to inspect the logs of A2Billing, and check what number is delivered to you, what A2Billing does to manipulate the number. The rate simulator will be useful as well in diagnosing your issues.

Joe

provided by Star2Billing S.L.

RateEngine problem

Who is online