[asterisk-users] DAHDI/1-2 v. DAHDI/2-1 ??

[sean darcy]

sean darcy wrote:
> I've got a single TDM 400P board with two internal ports and 1 external.
> 
> chan_dahdi.conf:
> 
> context=internal      ; Uses the [internal] context in extensions.conf
> signalling=fxo_ks     ; fxo_ks not auto  Use FXO signalling for FXS
> group=0
> channel => 1          ; Telephone attached to port 1
> channel => 2          ; Telephone attached to port 2
> 
> context=incoming-pstn-line  ; Incoming calls go to [incoming-pstn-line]
> signalling=fxs_ks     ; fxs_ks not auto Use FXS signalling for FXO
> faxdetect=incoming
> busydetect=yes
> group=1
> channel => 4
> 
> But look at what happens when the first internal line and the external 
> line is busy and a sip call comes in:
> 
>      -- Executing [s at incoming:3] Dial("SIP/sip-0000000d", "DAHDI/g0,60") 
> in new stack
>      -- Called g0
>      -- DAHDI/1-2 is ringing
> 
> If the first line is free, everything works:
> 
>      -- Executing [s at incoming:3] Dial("SIP/sip-0000000e", "DAHDI/g0,60") 
> in new stack
>      -- Called g0
>      -- DAHDI/1-1 is ringing
> 
> The second internal does NOT ring, because it is DAHDI/2-1:
> 
>      -- Starting simple switch on 'DAHDI/2-1'
>      -- Hungup 'DAHDI/2-1'
> 
> when I go off-hook on the second line. And the external line is DAHDI/4-1.
> 
> 
> Is this a bug, or am I missing something really obvious?
> 
> sean
> 

FWIW:
asterisk*CLI> dahdi show channels group 0
    Chan Extension  Context         Language   MOH Interpret 
Blocked    State
       1            internal                   default 
        In Service
       2            internal                   default 
        In Service


sean