Cannot accept incoming call on beronet's BN4S0


#1

Hi!

I’using asterisk CVS HEAD, with mISDN,mISDNuser from Jolly, and 09/06/2005 chan_misdn from Beronet’s Site.

I’ve tried also chan_misdn-0.1.0 with same results. Basic management and config files are from AMPortal (CVS HEAD)

When i’m using Digium’s TDM40 demo kit everything works fine. All incoming/outgoing calls are routed fine. With BN4S0 i can make outgoing calls fine.

Whenever i’m trying an outgoing call i have the following output:


L1: DL_STATUS! port:1
–> SDL_REL port:1
L2: L2Link Down! port:1
L1: DL_STATUS! port:1
–> SDL_ESTAB port:1
L2: L2Link Up! port:1
–> lib: NEW_CR Ind with l3id:20004 port:1
–> new_process: New L3Id: 20004
–> Pres:0
–> Screen:3
–> cap speech
I IND :SETUP pid:0 mode:TE addr:0 port:1
–> l3id:20004 cause:16 dad:9999999999 oad:8888888888 channel:1 port:1
$$$ find_chan: No channel found for oad:8888888888 dad:9999999999
–> Keypad:
–> Bearer: Speech
–> Codec: Alaw
–> orig Numplan: Unknown
–> dest Numplan: Nat. prefix 0
–> * NEW CHANNEL dad:09999999999 oad:8888888888 ctx:from-pstn Queuing chan 0x8192d50
Extension can never match, so disconnecting
$$$ Bchan Activated addr 0
I SEND:DISCONNECT port:1 pid:0 mode:TE addr:0
–> l3id:20004 cause:1 oad0:8888888888 dad0:09999999999 channel:1 port:1
GOT SETUP OK: port:1
Unhandled Message: prim 20181 len -22 from addr 0, dinfo 0 on port: 0
I IND :STATUS pid:0 mode:TE addr:0 port:1
–> l3id:20004 cause:101 dad:09999999999 oad:8888888888 channel:1 port:1
–> cause:101

This is misdn.conf
[general]
context=misdn
language=en
debug=4
tracefile=/tmp/misdn.trace
bridging=yes
stop_tone_after_first_digit=yes
append_digits2exten=no
nationalprefix=0
internationalprefix=00
volume=0
te_choose_channel=yes
early_bconnect=yes
dialplan=0
use_callingpres=1
l1_info_ok=yes
dynamic_crypt=no
crypt_prefix=**
crypt_keys=test,muh

[bri]
ports=1,2,3,4
context=from-pstn
presentation=not_screened
immediate=yes
hold_allowed=yes
language=en
callgroup=0
pickupgroup=0
nationalprefix=0
internationalprefix=00
msns=*

Thanks a lot for your time!

angel.


#2

Well replying to myself, the solution is on “incoming routing”. _X. incoming calls are handled ok now!