asterisk users - Sep 2005 - chan_capi-cm, Euro ISDN bus: 2 extensions on same BRI port not working

Hello,

I am using a system with an AVM ISDN PCI card (fcpci) and asterisk with 
chan_capi-cm-0.6. The hardware is connected to a Siemens Hipath 3550 PBX. As 
a BRI connection has 2 channels and allows 2 simultaneous calls, 
numbers/MSNs 6391 and 6392 were for provisioned for each channel. The system 
is working (partly, read on), the trick is the correct cable wiring and 
setup the PBX's port as "S0 Euro Bus".

Calls from asterisk to PBX are working ok, really nice! But calls from PBX 
to asterisk are partly working. Calls to 6391 are okay, but calls to 6392 
are not. They simply did not appear on the BRI port (checked with capi 
debug).

The problem seems to be something related to MSN routing. The PBX manual 
says it is possible to connect up to 64 devices in one S0/BRI port and even 
show the wiring diagram for that. However, there is not a clear way to 
define MSN x goes to channel 1, MSN y goes to channel 2 in the PBX 
management software. I am starting to think it is impossible to configure 
this through PBX...

The PBX manual and on-line help says (as far as I understood) MSNs are 
configured at the user station.... but, this time, I was unable to configure 
MSN x=>channel 1, MSN y=>channel 2 in the capi.conf file of chan_capi
which
acts as the station.

Actually, I am super-confused! Is it possible to configure the MSN routing 
as I explained? Is Siemens right, that is, it is up to the station to 
advertise it is "reachable" and its MSN? Will chan_capi + fcpci do
that?

Thanks in advance,

--hg

Don't know, but at least check your capi.conf.  I had a similar issue,
but from the telco > asterisk.

Regards,
Greg

[general]
nationalprefix=1
internationalprefix=011
rxgain=0.5
txgain=0.5
ulaw=yes        ;set this, if you live in u-law world instead of a-law
                 ;(2 makes sense for single BRI, 30 for PRI)

[ISDNL1]          ;this example interface gets name 'ISDN1' and may be
any;name not starting with 'g' or $;ntmode=yes      ;if isdn card
operates in nt mode, set this to yes
isdnmode=msn     ;'MSN' (point-to-multipoint) or 'DID' (direct
inward
dial);when using NT-mode, ptp shoul$;isdnmode=did     ;'MSN'
(point-to-multipoint) or 'DID' (direct inward dial);when using NT-mode,
ptp shou$;incomingmsn=*    ;allow incoming calls to this list of
MSNs/DIDs, * == any
incomingmsn=5912211    ;allow incoming calls to this list of MSNs/DIDs,
* == any
controller=1     ;capi controller number to use
group=1          ;dialout group
;prefix=0        ;set a prefix to calling number on incoming calls
;softdtmf=on      ;enable/disable software dtmf detection, recommended
for AVM cards
;relaxdtmf=on     ;in addition to softdtmf, you can use relaxed dtmf
detection
;accountcode=     ;Asterisk accountcode to use in CDRs
context=capi-in-5912211  ;context for incoming calls
holdtype=hold    ;when Asterisk puts the call on hold, ISDN HOLD will be
used. If
                 ;set to 'local' (default value), no hold is done and
Asterisk may
                 ;play MOH.
;immediate=yes   ;immediate start of pbx with extension 's' if no digits
were
                 ;received on incoming call (no destination number yet)
;echosquelch=1   ;_VERY_PRIMITIVE_ echo suppression
echocancel=yes
;echocancel=yes  ;EICON DIVA SERVER (CAPI) echo cancelation
                 ;(possible values: 'no', 'yes',
'force', 'g164',
'g165')
;echocancelold=yes;use facility selector 6 instead of correct 8
(necessary for older eicon drivers)
echotail=64     ;echo cancel tail setting
bridge=yes      ;native bridging (CAPI line interconnect) if available
callgroup=1     ;Asterisk call group
;deflect=8161000 ;deflect incoming calls to 1234567 if all B channels
are busy
devices=1        ;number of concurrent calls on this controller

[ISDNL2]
isdnmode=msn
incomingmsn=6930821
controller=1
callgroup=2
group=2
bridge=yes      ;native bridging (CAPI line interconnect) if available
context=capi-in-6930821
echocancel=no
devices=1                         

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of
huelbe_garcia@fastimap.com
Sent: Wednesday, September 28, 2005 8:36 PM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] chan_capi-cm,Euro ISDN bus: 2 extensions on
same BRI port not working

Hello,

I am using a system with an AVM ISDN PCI card (fcpci) and asterisk with
chan_capi-cm-0.6. The hardware is connected to a Siemens Hipath 3550
PBX. As a BRI connection has 2 channels and allows 2 simultaneous calls,
numbers/MSNs 6391 and 6392 were for provisioned for each channel. The
system is working (partly, read on), the trick is the correct cable
wiring and setup the PBX's port as "S0 Euro Bus".

Calls from asterisk to PBX are working ok, really nice! But calls from
PBX to asterisk are partly working. Calls to 6391 are okay, but calls to
6392 are not. They simply did not appear on the BRI port (checked with
capi debug).

The problem seems to be something related to MSN routing. The PBX manual
says it is possible to connect up to 64 devices in one S0/BRI port and
even show the wiring diagram for that. However, there is not a clear way
to define MSN x goes to channel 1, MSN y goes to channel 2 in the PBX
management software. I am starting to think it is impossible to
configure this through PBX...

The PBX manual and on-line help says (as far as I understood) MSNs are
configured at the user station.... but, this time, I was unable to
configure MSN x=>channel 1, MSN y=>channel 2 in the capi.conf file of
chan_capi which acts as the station.

Actually, I am super-confused! Is it possible to configure the MSN
routing as I explained? Is Siemens right, that is, it is up to the
station to advertise it is "reachable" and its MSN? Will chan_capi +
fcpci do that?

Thanks in advance,

--hg


_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

On Wed, 28 Sep 2005 huelbe_garcia@fastimap.com wrote:
> Hello,
> 
> I am using a system with an AVM ISDN PCI card (fcpci) and asterisk with
> chan_capi-cm-0.6. The hardware is connected to a Siemens Hipath 3550 PBX.
As a
> BRI connection has 2 channels and allows 2 simultaneous calls, numbers/MSNs
> 6391 and 6392 were for provisioned for each channel. The system is working
> (partly, read on), the trick is the correct cable wiring and setup the
PBX's
> port as "S0 Euro Bus".
> 
> Calls from asterisk to PBX are working ok, really nice! But calls from PBX
to
> asterisk are partly working. Calls to 6391 are okay, but calls to 6392 are
> not. They simply did not appear on the BRI port (checked with capi debug).
> 
> The problem seems to be something related to MSN routing. The PBX manual
says
> it is possible to connect up to 64 devices in one S0/BRI port and even show
> the wiring diagram for that. However, there is not a clear way to define
MSN x
> goes to channel 1, MSN y goes to channel 2 in the PBX management software.
I
> am starting to think it is impossible to configure this through PBX...
> 
> The PBX manual and on-line help says (as far as I understood) MSNs are
> configured at the user station.... but, this time, I was unable to
configure
> MSN x=>channel 1, MSN y=>channel 2 in the capi.conf file of chan_capi
which
> acts as the station.
> 
> Actually, I am super-confused! Is it possible to configure the MSN routing
as
> I explained? Is Siemens right, that is, it is up to the station to
advertise
> it is "reachable" and its MSN? Will chan_capi + fcpci do that?
No, your PBX must be configured to signal a call to these MSNs on that 
S0 port.
In capi.conf you just specify which MSNs shall be signaled to Asterisk.
Using incomingmsn=* means all MSNs and the extensions.conf can decide what 
to do with it.

If you have a verbose level of 5 and set 'capi debug', you should see at
least a CONNECT_IND message on a call. If you don't see that, than the PBX 
is not signaling this call on that S0 port. In that case, chan_capi and me 
cannot help you, it's an PBX issue.

Armin