asterisk users - Mar 2006 - interop problem: "Missing handling for mandatory IE 24 (cs0, Channel Identification)"

Hi everybody,

I've connected Asterisk 1.2.5 (libpri 1.2.2, zaptel 1.2.4, Linux 2.6.13.2)
to
an Avaya-Tenovis PBX via a PRI/E1-line. Calls from SIP-phones via * to the 
PBX work fine. However, incoming calls to * only result in:
--
XXX Missing handling for mandatory IE 24 (cs0, Channel Identification) XXX
--
which seems to be an * problem, because a Windows-fax-machine works fine on a 
PRI line with the same configuration. 

I was able to get it to work somehow by commenting out the following block in 
libpri/q931.c, line 3194:
--
/* JH
        for (x=0;x<MAX_MAND_IES;x++) {
                if (mandies[x]) {
[...]
                }
        }
*/
--
However, as Avaya-Tenovis PBXes are probably not so uncommon, this should IMHO 
be fixed properly as it's a major * interop problem...

Full "pri debug span 1" output:
--
*CLI> pri debug span 1
Enabled debugging on span 1
< Protocol Discriminator: Q.931 (8)  len=34
< Call Ref: len= 2 (reference 98/0x62) (Originator)
< Message type: SETUP (5)
< [04 03 80 90 a3]
< Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer
capability:
Speech (0)
<                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode 
(16)
<                              Ext: 1  User information layer 1: A-Law (35)
< [xc xd x1 x0 x8 x4 x2 x1 x9 x0 x2 x8 x2 x5 x0]
< Calling Number (len=15) [ Ext: 0  TON: National Number (2)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
<                           Presentation: Presentation permitted, user number
not screened (0) 'xx21xxxx250' ]
< [70 03 81 30 30]
< Called Number (len= 5) [ Ext: 1  TON: Unknown Number Type (0)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '00' ]
< [7d 02 91 81]
< IE: High-layer Compatibility (len = 4)
-- Making new call for cr 98
-- Processing Q.931 Call Setup
-- Processing IE 4 (cs0, Bearer Capability)
-- Processing IE 108 (cs0, Calling Party Number)
-- Processing IE 112 (cs0, Called Party Number)
-- Processing IE 125 (cs0, High-layer Compatibility)
XXX Missing handling for mandatory IE 24 (cs0, Channel Identification)
XXX
> Protocol Discriminator: Q.931 (8)  len=9
> Call Ref: len= 2 (reference 98/0x62) (Terminator)
> Message type: RELEASE COMPLETE (90)
> [08 02 81 e0]
> Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0   Location: 
Private network serving the local user (1)
>                  Ext: 1  Cause: Unknown (96), class = Protocol Error (6) ]
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null

*CLI>
--

/proc/zaptel/1:
--
Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" HDB3/CCS/CRC4

           1 WCT1/0/1 Clear (In use)
           2 WCT1/0/2 Clear (In use)
           3 WCT1/0/3 Clear (In use)
           4 WCT1/0/4 Clear (In use)
           5 WCT1/0/5 Clear (In use)
           6 WCT1/0/6 Clear (In use)
           7 WCT1/0/7 Clear (In use)
           8 WCT1/0/8 Clear (In use)
           9 WCT1/0/9 Clear (In use)
          10 WCT1/0/10 Clear (In use)
          11 WCT1/0/11 Clear (In use)
          12 WCT1/0/12 Clear (In use)
          13 WCT1/0/13 Clear (In use)
          14 WCT1/0/14 Clear (In use)
          15 WCT1/0/15 Clear (In use)
          16 WCT1/0/16 HDLCFCS (In use)
          17 WCT1/0/17 Clear (In use)
          18 WCT1/0/18 Clear (In use)
          19 WCT1/0/19 Clear (In use)
          20 WCT1/0/20 Clear (In use)
          21 WCT1/0/21 Clear (In use)
          22 WCT1/0/22 Clear (In use)
          23 WCT1/0/23 Clear (In use)
          24 WCT1/0/24 Clear (In use)
          25 WCT1/0/25 Clear (In use)
          26 WCT1/0/26 Clear (In use)
          27 WCT1/0/27 Clear (In use)
          28 WCT1/0/28 Clear (In use)
          29 WCT1/0/29 Clear (In use)
          30 WCT1/0/30 Clear (In use)
          31 WCT1/0/31 Clear (In use)
--

zapata.conf:
--
[channels]
context => from_pbx
switchtype => euroisdn
signalling => pri_cpe
callerid = asreceived
group => 1
channel =>  1-15
channel => 17-31
--

Cheers, Johann

Hi,
> < Message type: SETUP (5)
...
> XXX Missing handling for mandatory IE 24 (cs0, Channel Identification) XXX
According to ETS 300 102 (the european ISDN specification), section 
3.1.16 a SETUP message must contain an IE 'Channel Identification' which
is mandatory for network to user direction (see note 4 of table 3.16).

Seems that you have to change the setup of your Avaya system. For e.g. 
try changing network and user mode or configure a SIP-trunk if your 
Avaya-PBX supports it.

Deti