asterisk users - Nov 2008 - Dahdi, b410p and looping from 1 port to another

Hello,

Is it possible, for testing, to connect an cat5 straight patch cord between
2 ports of a Digium B410P card and use these 2 ports as a normal dahdi trunk
?

I've tried this:

One port is set as NT, the other as TE.

I would expect timing to come for system hardware so I choose in
/etc/dahdi/system.conf :
span=1,0,0,ccs,ami
span=2,0,0,ccs,ami


Results:
- both ports lights are green
- console shows the outgoing call
- no call is coming in and nothing happens (no sound, no message on console)

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20081126/608b11d1/attachment.htm

Olivier wrote:
> One port is set as NT, the other as TE.
> 
> I would expect timing to come for system hardware so I choose in
> /etc/dahdi/system.conf :
> span=1,0,0,ccs,ami
> span=2,0,0,ccs,ami
What is your configuration in chan_dahdi.conf?

-- 
Kevin P. Fleming
Director of Software Technologies
Digium, Inc. - "The Genuine Asterisk Experience" (TM)

Hi,

On Wed, Nov 26, 2008 at 04:12:58PM +0100, Olivier wrote:
> Hi,
> 
> From your answer, shall I understand it is possible to loop for one port
> back to another ?
> 
> /etc/dahdi/system.conf :
> span=1,0,0,ccs,ami
> span=2,0,0,ccs,ami
Hmm...  which of those two should provide timing?

I suppose you should use something of the sort of:

span=1,1,0,ccs,ami
span=2,0,0,ccs,ami
> Anyway, chan_dahdi.conf :
> 
> [channels]
> language=fr
> context=isdntrunk
> switchtype=euroisdn
> pridialplan=unknown
> prilocaldialplan=unknown
> internationalprefix=00
> nationalprefix=0
> usecallerid=yes
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> signalling=bri_cpe_ptp
> channel=>1-2
> channel=>4-5
s/bri_cpe_ptp/bri_cpe/

In addition to that, a CPE needs to talk to a Network on the other side. 
Thus you should have something of the sort of:

signalling=bri_net
channel=>1-2
signalling=bri_cpe
channel=>4-5


(As for the question of wiring: I have no idea. Refer to the
documentation or to the answers of others in this thread)

-- 
               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

Hi,

Hardware is b410p with :
- span1 jumpers set to NT (no 100 ohm termination)
- span2 jumpers set to TE (no 100 ohm termination)
- straight cable from port1 to port2

Scheme:

--------------------
                   1----------
                   |          |   <------ cat5 patch cord
                   2----------
   B410P      |
                   3
                   |
                   4
                   |
--------------------



/etc/dahdi/system.conf :
span=1,0,0,ccs,ami
bchan=1,2
dchan=3
span=2,1,0,ccs,ami
bchan=4,5
dchan=6


/etc/asterisk/chan_dahdi.conf:
context=isdntrunk
group=1
callgroup=1
pickupgroup=1
immediate=no

signalling=bri_cpe
channel=>1-2
signalling=bri_net
channel=>4-5

/etc/asterisk/extensions.ael
...
context mylocal {
        _10. => {
                Dial(DAHDI/g1/${EXTEN:1});
                Hangup();
        };
        _753[0356] => {
                Dial(SIP/${EXTEN});
                Hangup();
        };
};

context isdntrunk {
        _X. => {
                NoOp(Call from ${CALLERID(num)});
                Dial(SIP/7530);
                Hangup();
        };
        s => {
                NoOp(Call from ${CALLERID(num)});
                Dial(SIP/7530);
                Hangup();
        };
};

# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
   wct4xxp: done   wcte12xp: done   wct1xxp: done   wcte11xp: done
wctdm24xxp: done   wcfxo: done   wctdm: done   wcb4xxp: done   xpp_usb: done
Running dahdi_cfg: done.

# dahdi_cfg -vvv
DAHDI Tools Version - 2.1.0-rc5

DAHDI Version: 2.1.0-rc5
Echo Canceller(s):
Configuration
=====================
SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: D-channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: D-channel (Default) (Slaves: 06)

6 channels to configure.

# /etc/init.d/asterisk start
# asterisk -r

after dialing 10123456789
Executing [10123456789 at mylocal:1] Dial("SIP/7533-095aaae0",
"DAHDI/g1/0123456789") in new stack
[Dec  1 09:59:22] WARNING[5011]: app_dial.c:1739 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)
  == Everyone is busy/congested at this time (1:0/1/0)




Is there something obvious in configuration keeping this "self-looping
trunk" to work ?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20081201/4e941cb7/attachment-0001.htm

On 1 Dec 2008, at 09:09, Olivier wrote:
> Is there something obvious in configuration keeping this "self- 
> looping trunk" to work ?
You are not using a crossover cable?

On Mon, Dec 01, 2008 at 10:09:06AM +0100, Olivier wrote:
> Hi,
> 
> Hardware is b410p with :
> - span1 jumpers set to NT (no 100 ohm termination)
> - span2 jumpers set to TE (no 100 ohm termination)
> - straight cable from port1 to port2
> 
> Scheme:
> 
> --------------------
>                    1----------
>                    |          |   <------ cat5 patch cord
>                    2----------
>    B410P      |
>                    3
>                    |
>                    4
>                    |
> --------------------
> 
> 
> 
> /etc/dahdi/system.conf :
> span=1,0,0,ccs,ami
> bchan=1,2
> dchan=3
> span=2,1,0,ccs,ami
> bchan=4,5
> dchan=6
s/dchan/hardhdlc/

This is one of the defaults that needs changing in dahdi_genconf .
Probably will happen when we fix our BRI driver to support hardhdlc :-)

-- 
               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

> For a ptmp setup where you have multiple phones. 
Or even a single phone if the port is set to ptmp.

Proof of this point is the way I am using our B410P card.  Ports 1 and 2
are TE (ptp) and ports 3 & 4 are NT (ptmp).

I have a single ISDN modem connected to port 3 and the B410P would not
even look at it unless the 100ohm termination was switched on.

So, to reiterate - ptp needs no 100ohm termination (because the end
point provides it - aka TEI 0, but ptmp does - aka TEI 127).

Looks like we are going to agree to disagree on this one.