Topic: Does mISDN come as part of SAIL 3.1.1-22 ?

[fred2k3]

Hello,

I'm trying to build a SAIL PBX using 3.1.1-22 (which uses SME 8 and Asterisk 1.8 ) I'm pretty much a complete beginner with any sort of Linux system so I'm probably overlooking some very basic things. What I'm stuggling with atm is getting the ISDN working. I can see from the SAIL web interface that the card is recognised (from the PCI cards screen) and I'm trying to setup a trunk for it.

I've been told I need mISDN to get this working. If I run mISDN commands from SME at the moment it says "-bash: mISDN: command not found" so I'm guessing it's not installed at the moment. I tried to follow this: https://www.misdn.eu/wiki/Howto_for_Debian/  but git commands don't work either. Is git part of SME or do I need to download that too?

Is downloading the mISDN git file even the best way to proceed here or am I barking up the wrong tree?!

Any help hugely appreciated 

[SARK devs]

Hi there

No, you don't need mISDN.  Digium integrated ISDN2 support into Dahdi sometime in the 2.x release (not sure when) so you don't need to install mISDN anymore.   It all just works from Dahdi.

If you can see the card in PCI cards then SARK should have automatically created a trunk for you called DAHDIGroup0.   This is your outbound ISDN trunk.  You can route outbound calls to it by creating a route which selects the trunk.

Hope this helps.

Kind Regards

S

[fred2k3]

Many thanks, I will test this later.

[fred2k3]

The DAHDIGroup0 trunk is present and I have created an outbound route with a dialplan of _0XXXXXXXXXX with DAHDIGroup0 as the primary path. When I attempt to dial out from my extension I get an engaged tone. Looking at the asterisk trace I get the following error:

[Apr  2 17:37:22] WARNING[3842]: channel.c:5522 ast_request: No channel type registered for 'DAHDI'
[Apr  2 17:37:22] WARNING[3842]: app_dial.c:2198 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 66 - Channel not implemented)

Can anyone advise how I go about setting up this channel please?


Full Asterisk log here:

== Using SIP RTP CoS mark 5
    -- Executing [0775xxxxxxx@internal:1] AGI("SIP/6005-00000000", "sarkhpe,OutCos,0775xxxxxxx,,") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/sarkhpe
    -- <SIP/6005-00000000>AGI Script sarkhpe completed, returning 0
    -- Executing [0775xxxxxxx@6005opencos:1] AGI("SIP/6005-00000000", "sarkhpe,OutCluster, 0775xxxxxxx,,") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/sarkhpe
    -- AGI Script Executing Application: (Set) Options: (CDR(accountcode)=default)
    -- <SIP/6005-00000000>AGI Script sarkhpe completed, returning 0
    -- Executing [0775xxxxxxx @qrxvtmny:1] AGI("SIP/6005-00000000", "sarkhpe,OutRoute,DEFAULT,,") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/sarkhpe
    -- AGI Script Executing Application: (Set) Options: (TIMEOUT(absolute)=14400)
Channel will hangup at 2013-04-02 21:37:22.565 BST.
    -- AGI Script Executing Application: (Dial) Options: (DAHDI/g0/0775xxxxxxx,,T)
[Apr  2 17:37:22] WARNING[3842]: channel.c:5522 ast_request: No channel type registered for 'DAHDI'
[Apr  2 17:37:22] WARNING[3842]: app_dial.c:2198 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 66 - Channel not implemented)
  == Everyone is busy/congested at this time (1:0/0/1)
    -- AGI Script Executing Application: (Playback) Options: (beep)
    -- <SIP/6005-00000000> Playing 'beep.gsm' (language 'en-gb')
    -- AGI Script Executing Application: (Set) Options: (TIMEOUT(absolute)=14400)
Channel will hangup at 2013-04-02 21:37:23.352 BST.
    -- AGI Script Executing Application: (Dial) Options: (SIP/0775xxxxxxx@peer5103,,T)
  == Using SIP RTP CoS mark 5
    -- Called SIP/0775xxxxxxx@peer5103
[Apr  2 17:37:23] NOTICE[3393]: chan_sip.c:19661 handle_response_invite: Failed to authenticate on INVITE to '"6005" <sip:6005@92.xx.xxx.xxx>;tag=as4ed67c0f'
    -- SIP/peer5103-00000001 is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
    -- AGI Script Executing Application: (Playback) Options: (beep)
    -- <SIP/6005-00000000> Playing 'beep.gsm' (language 'en-gb')
    -- AGI Script Executing Application: (Playtones) Options: (congestion)
    -- AGI Script Executing Application: (Congestion) Options: ()
    -- <SIP/6005-00000000>AGI Script sarkhpe completed, returning 4
  == Spawn extension (qrxvtmny, 0775xxxxxxx, 1) exited non-zero on 'SIP/6005-00000000'
    -- Executing [h@qrxvtmny:1] Hangup("SIP/6005-00000000", "") in new stack
  == Spawn extension (qrxvtmny, h, 1) exited non-zero on 'SIP/6005-00000000'

[SARK devs]

at the linux cli what do the following commands return?

Code: [Select]

rpm -qa | grep dahdi
and

Code: [Select]

rpm -qa | grep asterisk
kind Regards

s

[fred2k3]

[root@voip01 ~]# rpm -qa | grep dahdi
dahdi-firmware-tc400m-MR6.12-1_centos5
dahdi-firmware-te820-1.76-1_centos5
kmod-dahdi-linux-fwload-vpmadt032-2.6.1-1_centos5.2.6.18_308.13.1.el5
asterisk18-dahdi-1.8.7.0-2_centos5
dahdi-firmware-oct6114-256-1.05.01-1_centos5
dahdi-firmware-vpmoct032-1.12.0-1_centos5
dahdi-firmware-oct6114-064-1.05.01-1_centos5
dahdi-tools-2.4.1-68.el5
kmod-dahdi-linux-2.6.1-1_centos5.2.6.18_308.13.1.el5
dahdi-firmware-hx8-2.06-1_centos5
dahdi-linux-2.6.1-1_centos5
dahdi-firmware-2.0.4-1_centos5
dahdi-firmware-oct6114-128-1.05.01-1_centos5


[root@voip01 ~]# rpm -qa | grep asterisk
asterisk-sounds-moh-opsound-alaw-0.0-4_centos5
asterisk18-addons-core-1.8.7.0-2_centos5
asterisk18-dahdi-1.8.7.0-2_centos5
asterisk18-core-1.8.7.0-2_centos5
asterisk18-configs-1.8.7.0-2_centos5
asterisk18-1.8.7.0-2_centos5
asterisk-sounds-core-en-alaw-1.4.21-1_centos5
asterisk18-voicemail-1.8.7.0-2_centos5
asterisk18-doc-1.8.7.0-2_centos5
asterisknow-version-2.0.0-4_centos5
asterisk18-addons-mysql-1.8.7.0-2_centos5

[SARK devs]

What kind of ISDN card do you have (manufacturer & model)?

At the asterisk console do the following and post the output.

Code: [Select]

dahdi show status
dahdi show channels
Kind Regards

S

[fred2k3]

Ok, originally I had the wrong sort of ISDN card. Now I've got an OpenVox B100P PCI ISDN BRI Card (I'm using ISDN2e in the UK). This was described as being Asterisk compatible. It shows up in SAIL as pci:0000:00:05.0     zaphfc-      1397:2bd0 HFC-S ISDN BRI card but doesn't create a dahdi trunk. I have re-installed the SAIL 3.1.1-22 ISO from scratch (no updates) and reinitialsed the card from the PCI menu, but it still doesn't create a dahdi trunk. I have created a "custom" trunk  manually with the Dial String Lead-in set to: DAHDI/g0

Also created a PTT_DiD_Group with my 6 digit extension number set to ring an IVR. When I dial the number nothing happens, and I get nothing showing in the asterisk trace.

dahdi show status
Description                              Alarms  IRQ    bpviol CRC    Fra Codi Options  LBO

dahdi show channels
Chan Extension  Context         Language   MOH Interpret        Blocked    State
 pseudo            default                    default                         In Service

rpm -qa | grep dahdi

Code: [Select]

dahdi-firmware-tc400m-MR6.12-1_centos5
dahdi-firmware-2.0.4-1_centos5
dahdi-firmware-te820-1.76-1_centos5
dahdi-firmware-oct6114-128-1.05.01-1_centos5
dahdi-firmware-hx8-2.06-1_centos5
kmod-dahdi-linux-fwload-vpmadt032-2.6.1-1_centos5.2.6.18_308.13.1.el5
dahdi-linux-2.6.1-1_centos5
asterisk18-dahdi-1.8.7.0-2_centos5
dahdi-firmware-oct6114-256-1.05.01-1_centos5
dahdi-firmware-vpmoct032-1.12.0-1_centos5
dahdi-firmware-oct6114-064-1.05.01-1_centos5
dahdi-tools-2.4.1-68.el5
kmod-dahdi-linux-2.6.1-1_centos5.2.6.18_308.13.1.el5
rpm -qa | grep asterisk

Code: [Select]

asterisk-sounds-core-en-alaw-1.4.21-1_centos5
asterisk18-voicemail-1.8.7.0-2_centos5
asterisk18-doc-1.8.7.0-2_centos5
asterisk-sounds-moh-opsound-alaw-0.0-4_centos5
asterisknow-version-2.0.0-4_centos5
asterisk18-addons-core-1.8.7.0-2_centos5
asterisk18-addons-mysql-1.8.7.0-2_centos5
asterisk18-dahdi-1.8.7.0-2_centos5
asterisk18-1.8.7.0-2_centos5
asterisk18-core-1.8.7.0-2_centos5
asterisk18-configs-1.8.7.0-2_centos5