provided by Star2Billing S.L.

SIP friend's destination (dnid) length limits to 10 digits. In other words, if I dial any destination number under 10 digits, it works fine, but more then 10 digits, it will get only first 10's. Can anyone point me to where i can fix this.

NOTE: if i dial via an access number such as calling card, it work fine (11 digits still work, but its only acting up when I have SIP friend registered and dial directly)

Thanks in advance,

Hi

This sounds like an issue with the phone, in as much as it it sending the dial command to Asterisk right after the 10th digit.

Does it make a difference if the numbers dialed begin with a 0 or not ?

Inspect the settings in your phone very carefully.

Joe

thank you for you reply, but i inspected and tested many times before i posted this topic. I think that i jump to the conclusion that the use_dnid function is bug, because it acting like that only when this use_dnid enabled

if i dial 011 in front i will get as long as i want. this is weird......something wrong...

It really does sound as if you have a USA Dial plan in your phone.

10, digits starting with 1-9 is the USA dialing pattern, so I still reckon that you have a dial plan in your phone which is causing his behavior.

A bug like this in A2Billing would have turned up years ago.

Jpe

I know you would like to help, but seriously, my a2b setting is every clearly, i have set prefix 1 to use US trunk which seperated from my internation trunk, i know its not from US dialplan, because i looked at my cli and see the agi_dnid it already a number with a missing last digit already. Can you tell me where the data for the array in a2billling.php line 90 from ($agi->request) its seem like there is a limitation on this string. but i dont know

Which proves that the number has already been truncated by the time A2Billing is invoked (see function get_agi_request_parameter in Class.A2Billing.php). If you're sure your Asterisk dialplan isn't stripping the missing digits perhaps you should entertain Joe's suggestion that your phone's dialplan is the culprit.

thank you for you replying

I already looked at that function even try to swap these two things:

//$this->dnid = $agi->request['agi_dnid'];
$this->dnid = $agi->request['agi_extension'];

but nothing happened.

Modify your Asterisk dialplan to add something like: just before the DeadAGI(a2billing.php) call. You should see that Asterisk is receiving the truncated string.

you meean my like this

exten => _X.,n,NoOp(${EXTEN})
exten => _X.,1,DeadAGI(a2billing.php|2)
exten => _X.,2,Hangup

Added after 9 minutes:

maybe i havent told the whole story......

I have this mod, and im not sure if it interfering with it. here is what in my extensions_a2billing.conf

[a2billing-all]
exten => _X.,1,NoOp(${EXTEN})
exten => _X.,n,DeadAGI(a2billing.php|2)
exten => _X.,n,Hangup

[a2billing-sip]
exten => _1NXXNXXXXXX,1,Answer
exten => _1NXXNXXXXXX,n,Goto(ext-local2,${EXTEN},1)
exten => _1NXXNXXXXXX,n,DeadAGI(a2billing.php|2)
exten => _1NXXNXXXXXX,n,Hangup

include => a2billing-all

[ext-local2]
exten => _X.,1,Dial(SIP/${EXTEN:1},45,tr)
exten => _X.,2,DeadAGI(a2billing.php|2)
exten => _X.,3,Hangup

I dont see anything wrong with it, but is there anything wrong with it? right now my temp solution is used remove prefix and dial with 011.... but that extra dialing have to do.

That is stripping the first digit. Whether or not this is affecting you only you can tell.

I thought of that before and tried not to used that as well but it still acting the same way. Thank u very much for trying to hep. If u guys find anything new please let me know. I gave up on this thing already.

Hello again,

I just have some idea but do not know how to do it. I think that I can re-set the agi_dnid variable in the .conf, is that correct?

i have this problem too butonly with lynksys pap2v2.0 ,others adapters don't have problems

You serious? Thats my problem then. Im using pap2 ver.2 as well. Thamks for letting me know that. I was wasting my time on that then.

To my mind this lends yet more credence to Joe's original suggestion that you need to modify the adaptor's dialplan. I had a similar problem with the default dialplan on the Cisco ATA-186 which was easily worked around by editing the dialplan. I'm sure a similar tactic would also work on the Linksys now you're willing to accept that it might be the problem.