[Home]

Summary:ASTERISK-08176: q.931: IntID: Explicit seems not supported by MD110
Reporter:Philipp Kolmann (pkolmann)Labels:
Date Opened:2006-11-23 07:54:18.000-0600Date Closed:2011-06-07 14:02:48
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:We are currently upgrading our * 1.0.x box to the recent 1.2 version. We are having problems connecting asterisk to our Ericsson MD110 PBX:

-- Making new call for cr 32768
> Protocol Discriminator: Q.931 (8)  len=14
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> [18 04 e9 80 83 81]
> Channel ID (len= 6) [ Ext: 1  IntID: Explicit, PRI Spare: 0, Exclusive Dchan: 0
>                        ChanSel: Reserved
>                       Ext: 1  DS1 Identifier: 0  
>                       Ext: 1  Coding: 0   Number Specified   Channel Type: 3
>                       Ext: 1  Channel: 1 ]
> [79 01 80]
> Restart Indentifier (len= 3) [ Ext: 1  Spare: 0  Resetting Indicated Channel (0) ]
< Protocol Discriminator: Q.931 (8)  len=13
< Call Ref: len= 2 (reference 0/0x0) (Terminator)
< Message type: STATUS (125)
< [08 03 81 e4 18]
< Cause (len= 5) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0   Location: Private network serving the local user (1)
<                  Ext: 1  Cause: Invalid information element contents (100), class = Protocol Error (6) ]
<              Cause data 1: 18 (24)
< [14 01 00]
< Call State (len= 3) [ Ext: 0  Coding: CCITT (ITU) standard (0) Call state: Null (0)
-- Processing IE 8 (cs0, Cause)
-- Processing IE 20 (cs0, Call State)


Comparing the pri debug to version 1.0 we discovered that the IntID was changed to Explicit and the MD110 can't cope with this parameter.

We now disabled the disabled the svn ci from revision 222 and now asterisk works again for us.

A Solution may be to make this feature configurable by zapata.conf.

Thanks
Philipp Kolmann, Gabriel Kittel
Vienna University of Technology, Vienna, Austria
Comments:By: Matthew Fredrickson (mattf) 2006-11-25 22:53:43.000-0600

Can you post your zapata.conf?  IIRC, it should only be explicit if you setup your PRI in NFAS mode, using the new spanmap and family of options.
By: Philipp Kolmann (pkolmann) 2006-11-26 11:50:53.000-0600

Thanks for looking into this. Here is my current zapata.conf with the relevant lines:


[trunkgroups]
trunkgroup => 1,16
spanmap => 1,1

[channels]
language=en
context=enum
switchtype=euroisdn
internationalprefix = 00
nationalprefix = 0
localprefix = 01
privateprefix = 0158801
unknownprefix =
overlapdial=yes
priindication = outofband
signalling=pri_cpe

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
rxgain=0.0
txgain=0.0
group=1
channel => 1-15,17-31

immediate=no


I adopted it from the zapata file from 1.0. Thanks for any help,
Regards
Philipp Kolmann
By: Philipp Kolmann (pkolmann) 2006-11-26 12:25:29.000-0600

Regarding NFAS I checked http://www.voip-info.org/wiki-NFAS and wanted to note that we only have one PRI.
By: Matthew Fredrickson (mattf) 2006-11-28 13:07:38.000-0600

You're only supposed to use trunkgroup and spanmap with NFAS.  If you don't configure these options, it will pick the default dchannel (16) automatically, and not use the explicit identifier.  Try commenting those two lines out.  That should fix it.
By: Matthew Fredrickson (mattf) 2006-11-30 20:08:00.000-0600

Suspended due to lack of response.