[Asterisk-bsd] I4B by HPS + chan_capi + 1.4.8 on 6.2 = choppy audio & hangups

Hans Petter Selasky hselasky at c2i.net
Wed Jul 25 11:34:45 CDT 2007


On Tuesday 24 July 2007, Michael Iedema wrote:
> Greetings Everyone,
>
> I have a bit more info about my call setup problem. Below is a trace
> from the ISDN PBX that AskoziaPBX is attached to. It shows again a
> failed call and then a successful call directly afterward.
>
> The first call fails due to either AskoziaPBX not waiting for a
> Receiver Ready response long enough or the ISDN PBX waiting too long
> to send them. (lines 18-24)
>
> Regards,
> -Michael I.
>
>
> line, time, command/response, MSG, NR, NS, call-reference, layer-3
> // call 1 (fail)
> 04  10:29:25:078N  C  UI          Setup               o/106
> BEA:Speech  DSP:COMfortel  CGN:2600  CDN:2601  HLC:Telephony
> 07  10:29:25:078T  C  UI          Identity request    Ri:44375  Ai:127
> 08  10:29:25:078N  C  UI          Identity remove     Ri:0      Ai:72
> 09  10:29:25:078N  C  UI          Identity assigned   Ri:44375  Ai:81
> 12  10:29:25:281T  C  SABME
> 13  10:29:25:281T  C  INFO  0  0  Status Enquiry      o/127
> 14  10:29:25:281T  C  INFO  0  1  Status Enquiry      o/127
> 15  10:29:25:281N  R  UA
> 16  10:29:25:281N  R  RR    1
> 17  10:29:25:281N  R  RR    2
> 18  10:29:25:281T  C  INFO  0  2  Setup Acknowledge   d/106
> 19  10:29:25:281T  C  INFO  0  3  Call Proceeding     d/106
> 20  10:29:25:281T  C  INFO  0  4  Alerting            d/106
> 21  10:29:25:281N  R  RR    3
> 22  10:29:25:281N  R  RR    4
> 23  10:29:25:281N  R  RR    5
> 24  10:29:25:281N  C  INFO  5  0  Release             o/106
> CAU:Message not comp. with call state or type non-exist.
> 25  10:29:25:484T  C  RR    1

Can you get some more info why your PBX claims that "message not compatible 
with call state ...." in the following STATUS message:

> 26  10:29:25:484N  C  INFO  5  1  Status              o/106
> CAU:Message not comp. with call state or type non-exist.
> 27  10:29:25:484T  C  RR    2
> 30  10:29:29:203N  C  INFO  5  2  Release             o/106
> CAU:Message not comp. with call state or type non-exist.
> 31  10:29:29:390T  C  RR    3
>
> // call 2 (success)
> 48  10:29:37:343N  C  UI          Setup               o/107
> BEA:Speech  DSP:COMfortel  CGN:2600  CDN:2601  HLC:Telephony
> 51  10:29:37:359T  C  INFO  3  5  Setup Acknowledge   d/107
> 53  10:29:37:359N  R  RR    6
> 56  10:29:37:546T  C  INFO  3  6  Call Proceeding     d/107
> 57  10:29:37:546T  C  INFO  3  7  Alerting            d/107
> 58  10:29:37:546N  R  RR    7
> 59  10:29:37:546N  R  RR    8
> 62  10:29:41:750T  C  INFO  3  8  Connect             d/107
> 63  10:29:41:875N  R  RR    9
> 64  10:29:41:875N  C  INFO  9  3  Connect Acknowledge o/107
> 67  10:29:41:875T  C  RR    4
> 72  10:29:44:781T  C  INFO  4  9  Release Complete    d/107
> CAU:Normal call clearing
> 73  10:29:44:781N  R  RR    10

Also try setting a manual TEI value, by using the "-i " option when 
running "isdnconfig". See "man isdnconfig" for more info. Eg:

isdnconfig -u 9 -i 3 -p DRVR_DSS1_TE

If the command fails, you just have to upgrade I4B, hence the "-i" option was 
not functional in the code for some time.

--HPS



More information about the Asterisk-BSD mailing list