of course. With mISDN scenario i'm using asterisk-1.4.31 and mISDN and mISDNuser both in 1_1_9_2. First scan hardware and finally load modules with the follings outputs:
And this is the asterisk output with "core set verbose 3" and the file misdn.conf with "debug=1":
*CLI> P[ 1] I IND :NEW_CHANNEL oad: dad:958304495 pid:3 state:none P[ 1] Chan not existing at the moment bc->l3id:2000c bc:0x9b95864 event:NEW_CHANNEL port:1 channel:1 P[ 1] NO USERUESRINFO P[ 1] I IND :SETUP oad: dad:958304495 pid:3 state:none P[ 1] read_config: Getting Config P[ 1] I SEND:PROCEEDING oad: dad:0958304495 pid:3 -- Executing [0958304495@entrantes:1] Set("mISDN/1-u1", "=") in new stack -- Executing [0958304495@entrantes:2] Dial("mISDN/1-u1", "SIP/101") in new stack -- Called 101 -- SIP/101-00000001 is ringing P[ 1] * IND : ringing pid:3 P[ 1] I SEND:ALERTING oad: dad:0958304495 pid:3 == Spawn extension (entrantes, 0958304495, 2) exited non-zero on 'mISDN/1-u1' [May 14 10:26:11] DEBUG[21156]: chan_misdn.c:2531 misdn_hangup: misdn_hangup(mISDN/1-u1) P[ 1] * IND : HANGUP pid:3 ctx:entrantes dad:0958304495 oad: State:CLEANING P[ 0] handle_bchan: BC not found for prim:20081 with addr:52010101 dinfo:0 P[ 0] handle_bchan: BC not found for prim:f2481 with addr:55010180 dinfo:0
I can see "dad field" with my called number but the "oad field" dont contains the caller number.
Hello,
Some suggestions for you:
1. Base on your two audio files, there is no any callerid signal there. So I want to ask you that is it possible to directly insert ISDN line into the card? It will help us to troubleshoot where the issue is,right?
2.I suppose your ISDN line fine, then, Someone else proves that it works with this dialplan, please have a try:
A possible solution:
exten => xxxx,n,SetCallerPres(allowed)
exten => xxxx,n,Dial(SIP/phone)
3. If both of them are not help you, could you try other combinations of softwares(mISDN,mISDNuser)?
i'm going to try connect isdn directly to the card and paste here the results. Before the first post i tested with mISDN & mISDuser versions 1_1_7_1, 1_1_7_2 and 1_1_8 with asterisk 1.4.24 and give me the same result. Bristuff and zaptel system work too except in giving callerid.
i think the problem is with something related with isdn infraestructure although except callerid, all in the sequence of the call seems normal.
has spent some time but I think I should write the solution.
Solution: software and drivers used was run perfectly.provider acknowledged at the end does not providing the callerid though at first they said the opposite.