[asterisk-users] DAHDI - BRI - Astribank

[Tzafrir Cohen]

On Mon, Nov 30, 2009 at 10:41:23PM +0100, Aldo Bergamini wrote:
> Hello List,
> 
> it is a very long time since I wrote here.... It has been still in  
> Zaptel times....
> 
> Today I am run into a related problem: I can't get a DAHDI setup to  
> work 100%. I am configuring an Astribank XR00013 (BRI, two ISDN ports).
> 
> At some degree the installation (latest DAHDI drivers, Asterisk  
> 1.6.0.18 on Centos 5.x) works.
> I can get incoming calls to the dialplan context that is setup as  
> target. The call quality is good, etc.
> 
> The problem is on the other side, the outgoing route.
> There I get just rejected calls.


Is this Asterisk 1.4? If so, my first guess would be that you need to
set (in /etc/asterisk/chan_dahdi.conf )

  pridialplan = unknown

[snip]

> chan_dahdi.conf
> **********
> ;
> ; DAHDI telephony
> ;
> ; Configuration file
> 
> [trunkgroups]
> 
> [channels]
> 
> language=it
> ;context=from-pstn
> ;signalling=fxs_ks
> ;rxwink=300              ; Atlas seems to use long (250ms) winks
> ;
> ; Whether or not to do distinctive ring detection on FXO lines
> ;
> ;usedistinctiveringdetection=yes
> 
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=no
> ;echotraining=800
> rxgain=0.0
> txgain=0.0
> group=0
> callgroup=1
> pickupgroup=1
> immediate=no
> 
> ;faxdetect=both
> ;faxdetect=incoming
> ;faxdetect=outgoing
> faxdetect=no
> 
> ;Include setup-pstn configs
> 
> ;internationalprefix = 00
> ;nationalprefix = 0

; Instead of those:
pridialplan = unknown

And as we can see in the trace:


>      -- Executing [s at macro-OutcallsRouter:39] Set("SIP/ 
> 23001-0000000f", "CALLERID(num)=221591030") in new stack
>      -- Executing [s at macro-OutcallsRouter:40] NoOp("SIP/ 
> 23001-0000000f", "<Dial(DAHDI/g0/191,120)>") in new stack
>      -- Executing [s at macro-OutcallsRouter:41] Dial("SIP/ 
> 23001-0000000f", "DAHDI/g0/191,120") in new stack
>      -- Requested transfer capability: 0x00 - SPEECH
>      -- Called g0/191
>      -- DAHDI/1-1 is proceeding passing it to SIP/23001-0000000f
>      -- Channel 0/1, span 1 got hangup request, cause 63
>      -- Hungup 'DAHDI/1-1'
>    == Everyone is busy/congested at this time (1:0/0/1)
> **********
> 
> And this is from the PRI debug
> **********
> -- Making new call for cr 32776
>  > Protocol Discriminator: Q.931 (8)  len=32
>  > Call Ref: len= 1 (reference 8/0x8) (Originator)
>  > Message type: SETUP (5)
>  > [04 03 80 90 a3]
>  > Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer  
> capability: Speech (0)
>  >                              Ext: 1  Trans mode/rate: 64kbps,  
> circuit-mode (16)
>  >                                User information layer 1: A-Law (35)
>  > [18 01 81]
>  > Channel ID (len= 3) [ Ext: 1  IntID: Implicit  Other  Spare: 0   
> Preferred  Dchan: 0
>  >                        ChanSel: B1 channel
>                           ]
>  > [6c 0b 21 80 32 32 31 35 39 31 30 33 30]
>  > Calling Number (len=13) [ Ext: 0  TON: National Number (2)  NPI:  
> ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>  >                           Presentation: Presentation permitted,  
> user number not screened (0)  'xxxxxxxx' ]

The number you dialed is actually not 'xxxxxxxx'. Figuring it out from
the trace is left as an exercise to the reader. However you told the
telco that this was a "national" number, and I guess this is not the
case. The telco then considered it a wrong number due to e.g. an extra
prefix.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir