TE110P initialisation

Hi,

We’ve been using a Digium TE110P on a 6 channel PRI for two years, mostly successful. However one thing we noted was that after a reboot the system would never receive calls unless an outgoing call had been made first. Once this happened, calls would then be received as normal. We never thought much of it is the machine was rarely rebooted.

However, we’ve now moved the card to a 30 channel PRI which cannot make outgoing calls, and thus (perhaps) the little work around we used before no longer works.

When dialling the line, it is rejected with an “out of order” message. There are no log message within Asterisk with pri intense debugging enabled, and nothing logged in dmesg. All the diagnostics commands we have say that the line is active and up. There are no alarms showing except a yellow alarm occasionally just after the driver is loaded, which is then cleared. I’ve tried enabled debugging on the kernel modules, but this only produces extra output on start up.

Is the card not being properly initialised until the initial successful outbound call? What else should I try?

pri show span 1
Primary D-channel: 16
Status: Provisioned, Up, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: -1
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3

cat /proc/zaptel/1

Span 1: WCT1/0 “Digium Wildcard TE110P T1/E1 Card 0” (MASTER) HDB3/CCS/CRC4
IRQ misses: 2

       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) 

… cut …
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)
… cut …
29 WCT1/0/29 Clear (In use)
30 WCT1/0/30 Clear (In use)
31 WCT1/0/31 Clear (In use)

Hello,

Actually I do not hear from any of our customers something similar with what you have posted (like calling out in order to receive calls). Usually on PRI trunks calls are received without problems and the issue is with the outgoing calls.

From what you have mentioned I understand that right now (a new PRI line with 30 channels - same provider?) you could not call outside - is it true? What about incoming calls?

Regarding outgoing calls - usually you have to set your callerID before you call out. This callerID should be set from a range that your provider have provided to you . In case you already use a valid callerID you have to “play” with PRI config parameters (like pridialplan) or to ask your provider support why they reject your call.

Regarding incoming call - my advice is the same - please ask your provider why you could not receive calls before you do not call out as It is not a normal behavior.

HTH,
Ioan

Both lines have previously been used with different equipment (a traditional PABX on the old PRI, and a modem concentrator on the new PRI) and could receive incoming calls with no problem. It is only with the TE110P that we have had this issue with not being able to receive.

This is the pri intense debugging when making an outgoing call. There are absolutely no messages received when an incoming call is attempted.

1 > Protocol Discriminator: Q.931 (8)  len=35
1 > Call Ref: len= 2 (reference 15/0xF) (Originator)
1 > Message type: SETUP (5)
1 > [04 03 80 90 a3]
1 > Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer capability: Speech (0)
1 >                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)
1 >                              Ext: 1  User information layer 1: A-Law (35)
1 > [18 03 a9 83 9e]
1 > Channel ID (len= 5) [ Ext: 1  IntID: Implicit  PRI  Spare: 0  Exclusive  Dchan: 0
1 >                        ChanSel: Reserved
1 >                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
1 >                       Ext: 1  Channel: 30 ]
1 > [6c 05 21 80 33 38 38]
1 > Calling Number (len= 7) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
1 >                           Presentation: Presentation permitted, user number not screened (0)  '388' ]
1 > [70 0b c1 31 32 39 36 XX XX XX XX XX XX]
1 > Called Number (len=13) [ Ext: 1  TON: Subscriber Number (4)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)  '1296XXXXXX' ]
1 < Protocol Discriminator: Q.931 (8)  len=9
1 < Call Ref: len= 2 (reference 15/0xF) (Terminator)
1 < Message type: RELEASE COMPLETE (90)
1 < [08 02 82 ac]
1 < Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Public network serving the local user (2)
1 <                  Ext: 1  Cause: Requested channel not available (44), class = Network Congestion (resource unavailable) (2) ]
1 > Protocol Discriminator: Q.931 (8)  len=13
1 > Call Ref: len= 2 (reference 0/0x0) (Originator)
1 > Message type: RESTART (70)
1 > [18 03 a9 83 9e]
1 > Channel ID (len= 5) [ Ext: 1  IntID: Implicit  PRI  Spare: 0  Exclusive  Dchan: 0
1 >                        ChanSel: Reserved
1 >                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
1 >                       Ext: 1  Channel: 30 ]
1 > [79 01 80]
1 > Restart Indentifier (len= 3) [ Ext: 1  Spare: 0  Resetting Indicated Channel (0) ]
1 < Protocol Discriminator: Q.931 (8)  len=12
1 < Call Ref: len= 2 (reference 0/0x0) (Terminator)
1 < Message type: STATUS (125)
1 < [08 02 82 d2]
1 < Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Public network serving the local user (2)
1 <                  Ext: 1  Cause: Identified channel does not exist (82), class = Invalid message (e.g. parameter out of range) (5) ]
1 < [14 01 00]
1 < Call State (len= 3) [ Ext: 0  Coding: CCITT (ITU) standard (0)  Call state: Null (0)