I’m testing/evaluating FreePBX Distro 3.211.63-5 (x64) with Asterisk 11 and DAHDI 2.11.14 installed on a bare metal box with HFC-S Cologne Chip based ISDN PCI Card (single port) to connect with an single BRI (not PRI) Euro-ISDN PSTN land-line.
I noticed that incoming external calls (no matter if the caller is a PSTN land-line or a mobile line number) are correctly routed to an extension I defined (e.g. Extension 100, a SIP Terminal) BUT those calls show up on Asterisk’s log like the Called number was without its very first digit (as example: if called number is 01234 56789 then the number reported on the Asterisk logs appears only as 1234 56789 without the very first 0 digit).
AFAIK the incoming route I set up shouldn’t alter any digit on incoming calls (per default it accepts any DID / any CID).
Any possible cross-reference with (g0/DAHDI) Trunk settings I should fix or with DAHDI Hardware settings (National/International type of number settings) ?
Here a log (is there a way to attach files - txt or png - here ?) of a call when an external Mobile 3994709093 calls the ISDN Land-line 0444333695 (which is the system’s ISDN Number, as example), please note the loss of the first digit 0 on 444333695 on this long log:
– Accepting call from ‘3994709093’ to ‘444333695’ on channel 0/1, span 1
– Executing [[email protected]:1] NoOp(“DAHDI/i1/3994709093-3”, “Catch-All DID Match - Found 444333695 - You probably want a DID for this.”) in new stack
– Executing [[email protected]:2] Goto(“DAHDI/i1/3994709093-3”, “ext-did,s,1”) in new stack
– Goto (ext-did,s,1)
– Executing [[email protected]:1] ExecIf(“DAHDI/i1/3994709093-3”, “1?Set(__FROM_DID=s)”) in new stack
– Executing [[email protected]:2] Gosub(“DAHDI/i1/3994709093-3”, “app-blacklist-check,s,1()”) in new stack
– Goto (macro-hangupcall,s,3)
– Executing [[email protected]:3] ExecIf(“DAHDI/i1/3994709093-3”, “0?Set(CDR(recordingfile)=)”) in new stack
– Executing [[email protected]:4] Hangup(“DAHDI/i1/3994709093-3”, “”) in new stack
== Spawn extension (macro-hangupcall, s, 4) exited non-zero on ‘DAHDI/i1/3994709093-3’ in macro ‘hangupcall’
== Spawn extension (macro-dial-one, h, 1) exited non-zero on ‘DAHDI/i1/3994709093-3’
== Spawn extension (macro-dial-one, s, 42) exited non-zero on ‘DAHDI/i1/3994709093-3’ in macro ‘dial-one’
== Spawn extension (macro-exten-vm, s, 14) exited non-zero on ‘DAHDI/i1/3994709093-3’ in macro ‘exten-vm’
== Spawn extension (from-did-direct, 100, 2) exited non-zero on ‘DAHDI/i1/3994709093-3’
– Hungup 'DAHDI/i1/3994709093-3’
Please note that regarding the 0444333695 number is made of 0444 (local prefix / area code prefix) and 333695.
Just another note: a call from land-line or mobile (in my country at least) to a land-line number is always started by dialling the whole number (made of a local prefix/area code - made of one, two or three [1-9] digits - and this area code always starts with a 0 followed by number) so 0x+number, 0xx+number or 0xxx+number (except for special emergency numbers which don’t have a local prefix).
Any idea ? where could be the issue ? what I do wrong ? Could be DAHDI Settings about National and International prefixes (0/00 as example) ?
It seem to me that changing those prefixes and restarting DAHDI as requested by FreePBX didn’t changed anything on incoming calls.
Best regards, Davide.
Edit 08/02/2013: I found a thread similar to mine here although that user didn’t wrote where was exactly his issue and what exactly he did to solve it (apart from telling that it regarded the way he configured DAHDI).