cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jims
New Contributor III

PSTN PRI issues - inbound CNAME outbound DID

Jump to solution

Hi.  Let me start with some background.  We have a 23 channel ISDN PRI (US, National, CPE) coming from the local telco (Frontier) to a Digium T1/PRI card in our Asterisk server.  I bought a Total Access 908e Second Gen with the intention of dropping the Digium card so I can virtualize the Asterisk box (and I'm trying to move all of our stuff to pure SIP).  This seems to be the reverse of how most people are using the TA900's; i.e. interfacing old PBX's with an ITSP.

So what I have is;

Local phone provider PRI to Adtran TA908e T1 0/3

Adtran TA90e Eth 0/1 (10.10.2.5) to Asterisk PBX (10.10.2.10)

The good news is that calling works great.  I can call inward and those calls are tagged with the correct inbound DID.  I can call out to external numbers.  But I have two problems;

1) All outbound calls use the default telephone number for the PRI even though I am passing the outbound DID number for an extension.

2) Inbound calls don't show the caller's name, only their telephone number.

Both of these problems are not present when using the Digium PRI card so I must have some settings goofed.

Here's my config for the TA908e;

!

!

! ADTRAN, Inc. OS version R10.9.0.E

! Boot ROM version 14.05.00.SA

! Platform: Total Access 908e (2nd Gen), part number 4242908L5

! Serial number CFG1037199

!

!

hostname "TA908e"

enable password REMOVED

!

!

clock timezone -5

!

ip subnet-zero

ip classless

ip default-gateway 10.10.2.1

ip routing

ipv6 unicast-routing

!

!

!

!

no auto-config

!

event-history on

no logging forwarding

no logging email

!

no service password-encryption

!

username "REMOVED" password "REMOVED"

!

!

no ip firewall alg msn

no ip firewall alg mszone

no ip firewall alg h323

!

!

!

!

!

!

!

!

no dot11ap access-point-control

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

interface eth 0/1

  ip address  10.10.2.5  255.255.255.0

  no shutdown

!

!

interface eth 0/2

  no ip address

  shutdown

!

!

!

!

interface t1 0/1

  shutdown

!

interface t1 0/2

  shutdown

!

interface t1 0/3

  tdm-group 1 timeslots 1-24 speed 64

  no shutdown

!

interface t1 0/4

  shutdown

!

!

interface pri 1

  role user

  connect t1 0/3 tdm-group 1

  no shutdown

!

!

interface fxs 0/1

  no shutdown

!

interface fxs 0/2

  no shutdown

!

interface fxs 0/3

  no shutdown

!

interface fxs 0/4

  no shutdown

!

interface fxs 0/5

  no shutdown

!

interface fxs 0/6

  no shutdown

!

interface fxs 0/7

  no shutdown

!

interface fxs 0/8

  no shutdown

!

!

interface fxo 0/0

  no shutdown

!

!

isdn-group 1

  connect pri 1

!

!

!

!

!

!

!

!

!

!

!

!

no tftp server

no tftp server overwrite

http server

no http secure-server

no snmp agent

no ip ftp server

no ip scp server

no ip sntp server

!

!

!

!

!

!

!

!

sip

sip udp 5060

no sip tcp

!

!

!

voice feature-mode network

voice forward-mode network

!

!

!

!

!

!

!

!

!

!

!

!

!

!

voice trunk T01 type isdn

  resource-selection circular descending

  connect isdn-group 1

  rtp delay-mode adaptive

!

voice trunk T11 type sip

  sip-server primary 10.10.2.10

!

!

voice grouped-trunk PROVIDER

  trunk T01

  accept $ cost 0

!

!

voice grouped-trunk PBX

  trunk T11

  accept $ cost 0

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

line con 0

  no login

!

line telnet 0 4

  login

  no shutdown

line ssh 0 4

  login local-userlist

  line-timeout 1440

  no shutdown

!

sntp server 10.10.2.10

!

!

!

!

end

From Asterisk's SIP.CONF;

[adtran_bc1]

type=peer

host=10.10.2.5

context=from_adtran_bc1

disallow=all

allow=ulaw

insecure=invite

directmedia=yes

dtmfmode=rfc2833

sendrpid=pai

trustrpid=yes

I can post some IDSN and SIP debug logs too.  Thanks!

Labels (2)
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

OK, I seem to have the outbound DID issue resolved.  The fix was to add ISDN number templates;

View/Delete ISDN Number Templates (TON/NPI)

The following list details the currently configured ISDN Number templates. To delete a template, click on the Delete button next to that template. You can use an existing template as the basis for a new template by clicking on a template row. The form above will be initialized to that template's values.

PrefixDial Plan TemplateType of Number (TON)Numbering Plan Indicator (NPI)
NXX-NXX-XXXXNationalE.164
1-NXX-NXX-XXXXNationalE.164
911NationalE.164
211NationalE.164

09:25:34.313 ISDN.L2_FMT PRI  1  ==============================================

09:25:34.313 ISDN.L2_FMT PRI  1  T Sapi:00 C/R:R Tei:00 INFO Ns:19  Nr:62  P:0

09:25:34.313 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:0083

09:25:34.313 ISDN.L2_FMT PRI  1    M - 05 SETUP      

09:25:34.313 ISDN.L2_FMT PRI  1     IE - 04 BEARER CAPABILITY   Len=3

09:25:34.313 ISDN.L2_FMT PRI  1          80 Xfer Cap.:SPEECH           

09:25:34.313 ISDN.L2_FMT PRI  1          90 Xfer Rate:64k  

09:25:34.313 ISDN.L2_FMT PRI  1          A2 Layer 1:G.711 U-Law   

09:25:34.313 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID          Len=3

09:25:34.313 ISDN.L2_FMT PRI  1          A1 Primary Rate

09:25:34.314 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT

09:25:34.314 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED

09:25:34.314 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO

09:25:34.314 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS

09:25:34.314 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER

09:25:34.314 ISDN.L2_FMT PRI  1          87 Channel:7

09:25:34.314 ISDN.L2_FMT PRI  1     IE - 28 DISPLAY             Len=11

09:25:34.314 ISDN.L2_FMT PRI  1             Office Fax

09:25:34.314 ISDN.L2_FMT PRI  1     IE - 6C CALLING PARTY #     Len=12

09:25:34.314 ISDN.L2_FMT PRI  1          21 Numb. Type:NATIONAL     

09:25:34.314 ISDN.L2_FMT PRI  1             Numb. Plan:E.164         

09:25:34.315 ISDN.L2_FMT PRI  1          80 Presentation:ALLOWED    

09:25:34.315 ISDN.L2_FMT PRI  1             Screening:USER PROVIDED

09:25:34.315 ISDN.L2_FMT PRI  1             Ph.# 1112223333

09:25:34.315 ISDN.L2_FMT PRI  1     IE - 70 CALLED PARTY #      Len=11

09:25:34.315 ISDN.L2_FMT PRI  1          A1 Numb. Type:NATIONAL     

09:25:34.315 ISDN.L2_FMT PRI  1             Numb. Plan:E.164         

09:25:34.315 ISDN.L2_FMT PRI  1             Ph.# 4445556666

09:25:34.346 ISDN.L2_FMT PRI  1  ==============================================

I still get an error after the setup message, but it's a different error and the DID Number is getting set and the call goes through.

09:25:34.346 ISDN.L2_FMT PRI  1  ==============================================

09:25:34.346 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:62  Nr:20  P:0

09:25:34.346 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:8083

09:25:34.346 ISDN.L2_FMT PRI  1    M - 7D STATUS     

09:25:34.346 ISDN.L2_FMT PRI  1     IE - 08 CAUSE               Len=2

09:25:34.346 ISDN.L2_FMT PRI  1          82 Location:LN

09:25:34.346 ISDN.L2_FMT PRI  1          E3 Cause:99 (BAD_INFO_ELEM)

09:25:34.346 ISDN.L2_FMT PRI  1     IE - 14 CALL STATE          Len=1

09:25:34.347 ISDN.L2_FMT PRI  1       01

09:25:34.380 ISDN.L2_FMT PRI  1  ==============================================

I'm going to start a new thread on the inbound caller ID name issue so people don't have to scroll through all this.  Thanks again for your help, Jay.

-Jim

View solution in original post

0 Kudos
8 Replies
jayh
Honored Contributor
Honored Contributor

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

Two separate issues, debug sip stack messages and debug isdn l2-formatted would likely be useful if this doesn't fix it.

Regarding outbound CLID to the PSTN - Are you sending ten digits (or whatever your provider is expecting)?  For example, if your SIP server sends just an extension or 7-digits then the provider may reject it and substitute the default number.

For example:  Your DIDs are 312-555-0100 through 312-555-0199.  Your SIP PBX sends the calling number as 555-0123.  In the trunk facing the provider, T01, add the following:

voice trunk T01 type isdn

match ani 555XXXX substitute 312555XXXX

You might also experiment with the Asterisk options for sendrpid=pai and try other choices if in fact you're sending ten digits.

For inbound caller name (CNAM), under the PRI interface try the following options, one of them should fix it:

interface pri 1

isdn name-delivery display

  -or-

isdn name-delivery setup

  -or-

isdn name-delivery proceeding

  -or-

isdn name-delivery auto

If these don't work turn on debug for sip stack messages and isdn l2-formatted and capture both an inbound and outbound call.

jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

Hi Jay,

I'd like to start with the outbound CLID if that's agreeable.  In the following logs, I am calling from my desk (on the Asterisk system) to a mobile phone and hanging up once it rings.  I've replaced my real desk number with 111-222-3333 and the mobile number with 444-555-6666.   Here's the ISDN L2 capture;

12:47:00.234 ISDN.L2_FMT PRI  1  ==============================================

12:47:00.235 ISDN.L2_FMT PRI  1  T Sapi:00 C/R:R Tei:00 INFO Ns:40  Nr:53  P:0

12:47:00.235 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:000B

12:47:00.235 ISDN.L2_FMT PRI  1    M - 05 SETUP    

12:47:00.235 ISDN.L2_FMT PRI  1     IE - 04 BEARER CAPABILITY   Len=3

12:47:00.235 ISDN.L2_FMT PRI  1          80 Xfer Cap.:SPEECH         

12:47:00.235 ISDN.L2_FMT PRI  1          90 Xfer Rate:64k

12:47:00.235 ISDN.L2_FMT PRI  1          A2 Layer 1:G.711 U-Law 

12:47:00.235 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID          Len=3

12:47:00.235 ISDN.L2_FMT PRI  1          A1 Primary Rate

12:47:00.236 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT

12:47:00.236 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED

12:47:00.236 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO

12:47:00.236 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS

12:47:00.236 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER

12:47:00.236 ISDN.L2_FMT PRI  1          8d Channel:13

12:47:00.236 ISDN.L2_FMT PRI  1     IE - 6C CALLING PARTY #     Len=12

12:47:00.236 ISDN.L2_FMT PRI  1          00 Numb. Type:UNKNOWN    

12:47:00.236 ISDN.L2_FMT PRI  1             Numb. Plan:UNKNOWN     

12:47:00.236 ISDN.L2_FMT PRI  1          80 Presentation:ALLOWED  

12:47:00.236 ISDN.L2_FMT PRI  1             Screening:USER PROVIDED

12:47:00.237 ISDN.L2_FMT PRI  1             Ph.# 1112223333

12:47:00.237 ISDN.L2_FMT PRI  1     IE - 70 CALLED PARTY #      Len=11

12:47:00.237 ISDN.L2_FMT PRI  1          80 Numb. Type:UNKNOWN    

12:47:00.237 ISDN.L2_FMT PRI  1             Numb. Plan:UNKNOWN     

12:47:00.237 ISDN.L2_FMT PRI  1             Ph.# 4445556666

12:47:00.289 ISDN.L2_FMT PRI  1  ==============================================

12:47:00.289 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:53  Nr:41  P:0

12:47:00.289 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:00.289 ISDN.L2_FMT PRI  1    M - 7D STATUS   

12:47:00.289 ISDN.L2_FMT PRI  1     IE - 08 CAUSE               Len=3

12:47:00.289 ISDN.L2_FMT PRI  1          82 Location:LN

12:47:00.289 ISDN.L2_FMT PRI  1          E4 Cause:100 (INVALID_ELEM_CONTENTS)

12:47:00.289 ISDN.L2_FMT PRI  1          6C Diagnostic:

12:47:00.290 ISDN.L2_FMT PRI  1     IE - 08 CAUSE               Len=3

12:47:00.290 ISDN.L2_FMT PRI  1          82 Location:LN

12:47:00.290 ISDN.L2_FMT PRI  1          AB Cause:43 (ACCESS_INFO_DISCARDED)

12:47:00.290 ISDN.L2_FMT PRI  1          6C Diagnostic:

12:47:00.290 ISDN.L2_FMT PRI  1     IE - 14 CALL STATE          Len=1

12:47:00.290 ISDN.L2_FMT PRI  1       01

12:47:00.291 ISDN.L2_FMT PRI  1  ==============================================

12:47:00.291 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:54  Nr:41  P:0

12:47:00.291 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:00.291 ISDN.L2_FMT PRI  1    M - 02 CALL_PROC

12:47:00.291 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID          Len=3

12:47:00.292 ISDN.L2_FMT PRI  1          A1 Primary Rate

12:47:00.292 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT

12:47:00.292 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED

12:47:00.292 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO

12:47:00.292 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS

12:47:00.292 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER

12:47:00.292 ISDN.L2_FMT PRI  1          8d Channel:13

12:47:01.788 ISDN.L2_FMT PRI  1  ==============================================

12:47:01.788 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:55  Nr:41  P:0

12:47:01.788 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:01.788 ISDN.L2_FMT PRI  1    M - 01 ALERTING 

12:47:01.788 ISDN.L2_FMT PRI  1     IE - 1E PROGRESS INDICATOR  Len=2

12:47:01.788 ISDN.L2_FMT PRI  1          84 Location:RLN

12:47:01.788 ISDN.L2_FMT PRI  1          88 Description:INBAND AUDIO AVAIL

12:47:09.337 ISDN.L2_FMT PRI  1  ==============================================

12:47:09.337 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:56  Nr:41  P:0

12:47:09.337 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:09.337 ISDN.L2_FMT PRI  1    M - 07 CONNECT  

12:47:09.337 ISDN.L2_FMT PRI  1     IE - 1E PROGRESS INDICATOR  Len=2

12:47:09.337 ISDN.L2_FMT PRI  1          84 Location:RLN

12:47:09.337 ISDN.L2_FMT PRI  1          82 Description:DEST. NOT ISDN 

12:47:09.338 ISDN.L2_FMT PRI  1  ==============================================

12:47:09.338 ISDN.L2_FMT PRI  1  T Sapi:00 C/R:R Tei:00 INFO Ns:41  Nr:57  P:0

12:47:09.338 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:000B

12:47:09.338 ISDN.L2_FMT PRI  1    M - 0F CONNECT_ACK

12:47:12.821 ISDN.L2_FMT PRI  1  ==============================================

12:47:12.821 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:57  Nr:42  P:0

12:47:12.821 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:12.821 ISDN.L2_FMT PRI  1    M - 45 DISCONNECT

12:47:12.822 ISDN.L2_FMT PRI  1     IE - 08 CAUSE               Len=2

12:47:12.822 ISDN.L2_FMT PRI  1          80 Location:U

12:47:12.822 ISDN.L2_FMT PRI  1          90 Cause:16 (NORMAL_CLEARING)

12:47:12.822 ISDN.L2_FMT PRI  1  ==============================================

12:47:12.822 ISDN.L2_FMT PRI  1  T Sapi:00 C/R:R Tei:00 INFO Ns:42  Nr:58  P:0

12:47:12.822 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:000B

12:47:12.823 ISDN.L2_FMT PRI  1    M - 4D RELEASE  

12:47:12.836 ISDN.L2_FMT PRI  1  ==============================================

12:47:12.836 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:58  Nr:43  P:0

12:47:12.836 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:800B

12:47:12.836 ISDN.L2_FMT PRI  1    M - 5A RELEASE_CMP

I'm assuming the response E4 Cause:100 (INVALID_ELEM_CONTENTS) is trying to tell me something.  Maybe it's choking on the name text? 

And here's a SIP debug where I do the same thing -- call from my desk to a mobile and hang up;

12:50:00.935 SIP.STACK MSG     Rx: UDP src=10.10.2.10:5060 dst=10.10.2.5:5060

12:50:00.935 SIP.STACK MSG         INVITE sip:4445556666@10.10.2.5 SIP/2.0

12:50:00.935 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK538ad235

12:50:00.935 SIP.STACK MSG         Max-Forwards: 70

12:50:00.935 SIP.STACK MSG         From: "Jim Storch" <sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:00.935 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>

12:50:00.936 SIP.STACK MSG         Contact: <sip:1112223333@10.10.2.10:5060>

12:50:00.936 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:00.936 SIP.STACK MSG         CSeq: 102 INVITE

12:50:00.936 SIP.STACK MSG         User-Agent: Asterisk PBX 11.6-cert1

12:50:00.936 SIP.STACK MSG         Date: Sun, 26 Jan 2014 17:50:00 GMT

12:50:00.936 SIP.STACK MSG         Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

12:50:00.936 SIP.STACK MSG         Supported: replaces, timer

12:50:00.937 SIP.STACK MSG         P-Asserted-Identity: "Jim Storch" <sip:1112223333@10.10.2.10>

12:50:00.937 SIP.STACK MSG         Content-Type: application/sdp

12:50:00.937 SIP.STACK MSG         Content-Length: 235

12:50:00.937 SIP.STACK MSG    

12:50:00.937 SIP.STACK MSG         v=0

12:50:00.937 SIP.STACK MSG         o=root 1597072175 1597072175 IN IP4 10.10.2.10

12:50:00.938 SIP.STACK MSG         s=Asterisk PBX 11.6-cert1

12:50:00.938 SIP.STACK MSG         c=IN IP4 10.10.2.10

12:50:00.938 SIP.STACK MSG         t=0 0

12:50:00.938 SIP.STACK MSG         m=audio 18282 RTP/AVP 0 101

12:50:00.938 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

12:50:00.938 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000

12:50:00.939 SIP.STACK MSG         a=fmtp:101 0-16

12:50:00.939 SIP.STACK MSG         a=ptime:20

12:50:00.939 SIP.STACK MSG         a=sendrecv

12:50:00.939 SIP.STACK MSG    

12:50:00.945 SIP.STACK MSG     Tx: UDP src=10.10.2.5:5060 dst=10.10.2.10:5060

12:50:00.945 SIP.STACK MSG         SIP/2.0 100 Trying

12:50:00.946 SIP.STACK MSG         From: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:00.946 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>

12:50:00.946 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:00.946 SIP.STACK MSG         CSeq: 102 INVITE

12:50:00.946 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK538ad235

12:50:00.946 SIP.STACK MSG         Contact: <sip:4445556666@10.10.2.5:5060;transport=UDP>

12:50:00.946 SIP.STACK MSG         Supported: 100rel,replaces

12:50:00.947 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

12:50:00.947 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e_2nd_Gen/R10.9.2.E

12:50:00.947 SIP.STACK MSG         Content-Length: 0

12:50:00.947 SIP.STACK MSG    

12:50:02.142 SIP.STACK MSG     Tx: UDP src=10.10.2.5:5060 dst=10.10.2.10:5060

12:50:02.142 SIP.STACK MSG         SIP/2.0 183 Session Progress

12:50:02.142 SIP.STACK MSG         From: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:02.142 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:02.143 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:02.143 SIP.STACK MSG         CSeq: 102 INVITEE4 Cause:100 (INVALID_ELEM_CONTENTS)

12:50:02.143 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK538ad235

12:50:02.143 SIP.STACK MSG         Contact: <sip:4445556666@10.10.2.5:5060;transport=UDP>

12:50:02.143 SIP.STACK MSG         Supported: 100rel,replaces

12:50:02.143 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

12:50:02.144 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e_2nd_Gen/R10.9.2.E

12:50:02.144 SIP.STACK MSG         Content-Type: application/sdp

12:50:02.144 SIP.STACK MSG         Content-Length: 202

12:50:02.144 SIP.STACK MSG    

12:50:02.144 SIP.STACK MSG         v=0

12:50:02.144 SIP.STACK MSG         o=- 1390758602 1 IN IP4 10.10.2.5

12:50:02.145 SIP.STACK MSG         s=-

12:50:02.145 SIP.STACK MSG         c=IN IP4 10.10.2.5

12:50:02.145 SIP.STACK MSG         t=0 0

12:50:02.145 SIP.STACK MSG         m=audio 10056 RTP/AVP 0 101

12:50:02.145 SIP.STACK MSG         a=silenceSupp:off - - - -

12:50:02.145 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

12:50:02.146 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000

12:50:02.146 SIP.STACK MSG         a=fmtp:101 0-15

12:50:02.146 SIP.STACK MSG    

12:50:07.730 SIP.STACK MSG     Tx: UDP src=10.10.2.5:5060 dst=10.10.2.10:5060

12:50:07.730 SIP.STACK MSG         SIP/2.0 200 OK

12:50:07.730 SIP.STACK MSG         From: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:07.730 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:07.730 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:07.731 SIP.STACK MSG         CSeq: 102 INVITE

12:50:07.731 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK538ad235

12:50:07.731 SIP.STACK MSG         Contact: <sip:4445556666@10.10.2.5:5060;transport=UDP>

12:50:07.731 SIP.STACK MSG         Supported: 100rel,replaces

12:50:07.731 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

12:50:07.731 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e_2nd_Gen/R10.9.2.E

12:50:07.732 SIP.STACK MSG         Content-Type: application/sdp

12:50:07.732 SIP.STACK MSG         Content-Length: 202

12:50:07.732 SIP.STACK MSG    

12:50:07.732 SIP.STACK MSG         v=0

12:50:07.732 SIP.STACK MSG         o=- 1390758602 1 IN IP4 10.10.2.5

12:50:07.732 SIP.STACK MSG         s=-

12:50:07.733 SIP.STACK MSG         c=IN IP4 10.10.2.5

12:50:07.733 SIP.STACK MSG         t=0 0

12:50:07.733 SIP.STACK MSG         m=audio 10056 RTP/AVP 0 101

12:50:07.733 SIP.STACK MSG         a=silenceSupp:off - - - -

12:50:07.733 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

12:50:07.733 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000

12:50:07.734 SIP.STACK MSG         a=fmtp:101 0-15

12:50:07.734 SIP.STACK MSG    

12:50:07.736 SIP.STACK MSG     Rx: UDP src=10.10.2.10:5060 dst=10.10.2.5:5060

12:50:07.736 SIP.STACK MSG         ACK sip:4445556666@10.10.2.5:5060;transport=UDP SIP/2.0

12:50:07.736 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK6fa8b7f7

12:50:07.737 SIP.STACK MSG         Max-Forwards: 70

12:50:07.737 SIP.STACK MSG         From: "Jim Storch" <sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:07.737 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:07.737 SIP.STACK MSG         Contact: <sip:1112223333@10.10.2.10:5060>

12:50:07.737 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:07.737 SIP.STACK MSG         CSeq: 102 ACK

12:50:07.737 SIP.STACK MSG         User-Agent: Asterisk PBX 11.6-cert1

12:50:07.738 SIP.STACK MSG         Content-Length: 0

12:50:07.738 SIP.STACK MSG    

12:50:07.740 SIP.STACK MSG     Rx: UDP src=10.10.2.10:5060 dst=10.10.2.5:5060

12:50:07.740 SIP.STACK MSG         UPDATE sip:4445556666@10.10.2.5:5060;transport=UDP SIP/2.0

12:50:07.740 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK1dd12415

12:50:07.740 SIP.STACK MSG         Max-Forwards: 70

12:50:07.740 SIP.STACK MSG         From: "Jim Storch" <sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:07.741 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:07.741 SIP.STACK MSG         Contact: <sip:1112223333@10.10.2.10:5060>

12:50:07.741 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:07.741 SIP.STACK MSG         CSeq: 103 UPDATE

12:50:07.741 SIP.STACK MSG         User-Agent: Asterisk PBX 11.6-cert1

12:50:07.741 SIP.STACK MSG         Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

12:50:07.742 SIP.STACK MSG         Supported: replaces, timer

12:50:07.742 SIP.STACK MSG         P-Asserted-Identity: "Jim Storch" <sip:1112223333@10.10.2.10>

12:50:07.742 SIP.STACK MSG         Content-Type: application/sdp

12:50:07.742 SIP.STACK MSG         Content-Length: 237

12:50:07.742 SIP.STACK MSG    

12:50:07.742 SIP.STACK MSG         v=0

12:50:07.743 SIP.STACK MSG         o=root 1597072175 1597072176 IN IP4 10.10.2.186

12:50:07.743 SIP.STACK MSG         s=Asterisk PBX 11.6-cert1

12:50:07.743 SIP.STACK MSG         c=IN IP4 10.10.2.186

12:50:07.743 SIP.STACK MSG         t=0 0

12:50:07.743 SIP.STACK MSG         m=audio 11786 RTP/AVP 0 101

12:50:07.744 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

12:50:07.744 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000E4 Cause:100 (INVALID_ELEM_CONTENTS)

12:50:07.744 SIP.STACK MSG         a=fmtp:101 0-16

12:50:07.744 SIP.STACK MSG         a=ptime:20

12:50:07.744 SIP.STACK MSG         a=sendrecv

12:50:07.744 SIP.STACK MSG    

12:50:07.748 SIP.STACK MSG     Tx: UDP src=10.10.2.5:5060 dst=10.10.2.10:5060

12:50:07.748 SIP.STACK MSG         SIP/2.0 501 Not Implemented

12:50:07.748 SIP.STACK MSG         From: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:07.748 SIP.STACK MSG         To: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:07.749 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:07.749 SIP.STACK MSG         CSeq: 103 UPDATE

12:50:07.749 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.10:5060;branch=z9hG4bK1dd12415

12:50:07.749 SIP.STACK MSG         Supported: 100rel,replaces

12:50:07.749 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

12:50:07.749 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e_2nd_Gen/R10.9.2.E

12:50:07.750 SIP.STACK MSG         Content-Length: 0

12:50:07.750 SIP.STACK MSG    

12:50:10.018 SIP.STACK MSG     Tx: UDP src=10.10.2.5:5060 dst=10.10.2.10:5060

12:50:10.019 SIP.STACK MSG         BYE sip:1112223333@10.10.2.10:5060;transport=UDP SIP/2.0

12:50:10.019 SIP.STACK MSG         From: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:10.019 SIP.STACK MSG         To: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:10.019 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:10.019 SIP.STACK MSG         CSeq: 1 BYE

12:50:10.019 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.5:5060;branch=z9hG4bK-80c-1f72aa-5c47a8d0

12:50:10.020 SIP.STACK MSG         Max-Forwards: 70

12:50:10.020 SIP.STACK MSG         Supported: 100rel,replaces

12:50:10.020 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

12:50:10.020 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e_2nd_Gen/R10.9.2.E

12:50:10.020 SIP.STACK MSG         Content-Length: 0

12:50:10.020 SIP.STACK MSG    

12:50:10.022 SIP.STACK MSG     Rx: UDP src=10.10.2.10:5060 dst=10.10.2.5:5060

12:50:10.023 SIP.STACK MSG         SIP/2.0 200 OK

12:50:10.023 SIP.STACK MSG         Via: SIP/2.0/UDP 10.10.2.5:5060;branch=z9hG4bK-80c-1f72aa-5c47a8d0;received=10.10.2.5

12:50:10.023 SIP.STACK MSG         From: <sip:4445556666@10.10.2.5>;tag=49a8470-7f000001-13c4-805-4186207-805

12:50:10.023 SIP.STACK MSG         To: "Jim Storch"<sip:1112223333@10.10.2.10>;tag=as6729c44b

12:50:10.023 SIP.STACK MSG         Call-ID: 55da2582738dedf42e4503df4402678b@10.10.2.10:5060

12:50:10.024 SIP.STACK MSG         CSeq: 1 BYE

12:50:10.024 SIP.STACK MSG         Server: Asterisk PBX 11.6-cert1

12:50:10.024 SIP.STACK MSG         Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

12:50:10.024 SIP.STACK MSG         Supported: replaces, timer

12:50:10.024 SIP.STACK MSG         Content-Length: 0

12:50:10.025 SIP.STACK MSG

Our PRI delivers inbound DIDs as seven digits and takes outbound CLID as ten.

Lastly, here's the Asterisk version of ISDN Debug making the same kind of call using the Digium card where the outbound CLID works;

[May 14 13:52:38] PRI Span: 1

[May 14 13:52:38] PRI Span: 1 > DL-DATA request

[May 14 13:52:38] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=59

[May 14 13:52:38] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:38] PRI Span: 1 > Message Type: SETUP (5)

[May 14 13:52:38] PRI Span: 1

[May 14 13:52:38] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=59

[May 14 13:52:38] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:38] PRI Span: 1 > Message Type: SETUP (5)

[May 14 13:52:38] PRI Span: 1 > [04 03 80 90 a2]

[May 14 13:52:38] PRI Span: 1 > Bearer Capability (len= 5) [ Ext: 1  Coding-Std: 0  Info transfer capability: Speech (0)

[May 14 13:52:38] PRI Span: 1 >                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)

[May 14 13:52:38] PRI Span: 1 >                                User information layer 1: u-Law (34)

[May 14 13:52:38] PRI Span: 1 > [18 03 a1 83 96]

[May 14 13:52:38] PRI Span: 1 > Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0  Preferred  Dchan: 0

[May 14 13:52:38] PRI Span: 1 >                       ChanSel: As indicated in following octets

[May 14 13:52:38] PRI Span: 1 >                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3

[May 14 13:52:38] PRI Span: 1 >                       Ext: 1  Channel: 22 Type: CPE]

[May 14 13:52:38] PRI Span: 1 > [1e 02 80 83]

[May 14 13:52:38] PRI Span: 1 > Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  0: 0  Location: User (0)

[May 14 13:52:38] PRI Span: 1 >                               Ext: 1  Progress Description: Calling equipment is non-ISDN. (3) ]

[May 14 13:52:38] PRI Span: 1 > [28 0b b1 4a 69 6d 20 53 74 6f 72 63 68]

[May 14 13:52:38] PRI Span: 1 > Display (len=11) Charset: 31 [ Jim Storch ]

[May 14 13:52:38] PRI Span: 1 > [6c 0c 21 81 34 31 39 32 38 32 34 32 35 38]

[May 14 13:52:38] PRI Span: 1 > Calling Party Number (len=14) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)

[May 14 13:52:38] PRI Span: 1 >                                 Presentation: Presentation allowed, User-provided, verified and passed (1)  '1112223333' ]

[May 14 13:52:38] PRI Span: 1 > [70 0b 80 35 36 37 32 31 35 30 31 30 31]

[May 14 13:52:38] PRI Span: 1 > Called Party Number (len=13) [ Ext: 1  TON: Unknown Number Type (0)  NPI: Unknown Number Plan (0)  '4445556666' ]

[May 14 13:52:39] PRI Span: 1

[May 14 13:52:39] PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=12

[May 14 13:52:39] PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent to originator)

[May 14 13:52:39] PRI Span: 1 < Message Type: STATUS (125)

[May 14 13:52:39] PRI Span: 1 < [08 02 82 e3]

[May 14 13:52:39] PRI Span: 1 < Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Public network serving the local user (2)

[May 14 13:52:39] PRI Span: 1 <                  Ext: 1  Cause: Info. element nonexist or not implemented (99), class = Protocol Error (e.g. unknown message) (6) ]

[May 14 13:52:39] PRI Span: 1 < [14 01 01]

[May 14 13:52:39] PRI Span: 1 < Call State (len= 3) [ Ext: 0  Coding: CCITT (ITU) standard (0)  Call state: Call Initiated (1)

[May 14 13:52:39] PRI Span: 1

[May 14 13:52:39] PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=10

[May 14 13:52:39] PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent to originator)

[May 14 13:52:39] PRI Span: 1 < Message Type: CALL PROCEEDING (2)

[May 14 13:52:39] PRI Span: 1 < [18 03 a1 83 96]

[May 14 13:52:39] PRI Span: 1 < Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0  Preferred  Dchan: 0

[May 14 13:52:39] PRI Span: 1 <                       ChanSel: As indicated in following octets

[May 14 13:52:39] PRI Span: 1 <                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3

[May 14 13:52:39] PRI Span: 1 <                       Ext: 1  Channel: 22 Type: CPE]

[May 14 13:52:39] Span 1: Processing event PRI_EVENT_PROCEEDING(13)

[May 14 13:52:40] PRI Span: 1

[May 14 13:52:40] PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=9

[May 14 13:52:40] PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent to originator)

[May 14 13:52:40] PRI Span: 1 < Message Type: PROGRESS (3)

[May 14 13:52:40] PRI Span: 1 < [1e 02 8a 81]

[May 14 13:52:40] PRI Span: 1 < Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  0: 0  Location: Network beyond the interworking point (10)

[May 14 13:52:40] PRI Span: 1 <                               Ext: 1  Progress Description: Call is not end-to-end ISDN; further call progress information may be available inband. (1) ]

[May 14 13:52:40] Span 1: Processing event PRI_EVENT_PROGRESS(17)

[May 14 13:52:41] PRI Span: 1

[May 14 13:52:41] PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=5

[May 14 13:52:41] PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent to originator)

[May 14 13:52:41] PRI Span: 1 < Message Type: CONNECT (7)

[May 14 13:52:41] Span 1: Processing event PRI_EVENT_ANSWER(8)

[May 14 13:52:41] PRI Span: 1

[May 14 13:52:41] PRI Span: 1 > DL-DATA request

[May 14 13:52:41] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=5

[May 14 13:52:41] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:41] PRI Span: 1 > Message Type: CONNECT ACKNOWLEDGE (15)

[May 14 13:52:41] PRI Span: 1

[May 14 13:52:41] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=5

[May 14 13:52:41] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:41] PRI Span: 1 > Message Type: CONNECT ACKNOWLEDGE (15)

[May 14 13:52:42] PRI Span: 1

[May 14 13:52:42] PRI Span: 1 > DL-DATA request

[May 14 13:52:42] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=9

[May 14 13:52:42] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:42] PRI Span: 1 > Message Type: DISCONNECT (69)

[May 14 13:52:42] PRI Span: 1

[May 14 13:52:42] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=9

[May 14 13:52:42] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:42] PRI Span: 1 > Message Type: DISCONNECT (69)

[May 14 13:52:42] PRI Span: 1 > [08 02 81 90]

[May 14 13:52:42] PRI Span: 1 > Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Private network serving the local user (1)

[May 14 13:52:42] PRI Span: 1 >                  Ext: 1  Cause: Normal Clearing (16), class = Normal Event (1) ]

[May 14 13:52:42] PRI Span: 1

[May 14 13:52:42] PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=5

[May 14 13:52:42] PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent to originator)

[May 14 13:52:42] PRI Span: 1 < Message Type: RELEASE (77)

[May 14 13:52:42] Span 1: Processing event PRI_EVENT_HANGUP(6)

[May 14 13:52:42] PRI Span: 1

[May 14 13:52:42] PRI Span: 1 > DL-DATA request

[May 14 13:52:42] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=9

[May 14 13:52:42] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:42] PRI Span: 1 > Message Type: RELEASE COMPLETE (90)

[May 14 13:52:42] PRI Span: 1

[May 14 13:52:42] PRI Span: 1 > Protocol Discriminator: Q.931 (8)  len=9

[May 14 13:52:42] PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 137/0x89) (Sent from originator)

[May 14 13:52:42] PRI Span: 1 > Message Type: RELEASE COMPLETE (90)

[May 14 13:52:42] PRI Span: 1 > [08 02 81 90]

[May 14 13:52:42] PRI Span: 1 > Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  Location: Private network serving the local user (1)

[May 14 13:52:42] PRI Span: 1 >                  Ext: 1  Cause: Normal Clearing (16), class = Normal Event (1) ]

Thank you again.

jayh
Honored Contributor
Honored Contributor

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

Invalid element contents is often an ISDN switch type mismatch.  Yours is the default NI-2, does this match the provider?  You might try ATT5 or another possibility.

Something interesting is that the Asterisk shows the calling number type as e.164 but actually sends it as domestic ten-digits.  True e.164 would be +1 followed by ten digits.  I'm not sure how to specify the numbering type on the TA900 but haven't needed to so I suspect this may be ISDN switch-type mismatch.  Is the CLID you are sending a valid number assigned to that trunk by the carrier?  You might have to involve the carrier. 

jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

Invalid element contents is often an ISDN switch type mismatch.  Yours is the default NI-2, does this match the provider?  You might try ATT5 or another possibility.


I'm pretty sure it's correct.  That's how the Digium card is configured.  But I did come in on a couple weekends and try all the carrier types.

Something interesting is that the Asterisk shows the calling number type as e.164 but actually sends it as domestic ten-digits.  True e.164 would be +1 followed by ten digits.  I'm not sure how to specify the numbering type on the TA900 but haven't needed to so I suspect this may be ISDN switch-type mismatch.

I could try setting the CLID to 1+DID.  I'll see if that does anything.

Is the CLID you are sending a valid number assigned to that trunk by the carrier?


Yep.

You might have to involve the carrier.


I've tried but they are ... difficult.  Verizon sold to a smaller company and it's been a pain to get support.   Our previous system was a Nortel CS1000 and I do wonder if there might be some exotic legacy settings.  OTOH, the Digium card is fat, dumb, and happy as so;


talk*CLI> pri show span 1

Primary D-channel: 24

Status: Up, Active

Switchtype: National ISDN

Type: CPE

Remote type: Network

Overlap Dial: 0

Logical Channel Mapping: 0

Timer and counter settings:

  N200: 3

  N202: 3

  K: 7

  T200: 1000

  T201: 1000

  T202: 10000

  T203: 10000

  T303: 4000

  T305: 30000

  T308: 4000

  T309: 6000

  T312: 6000

  T313: 4000

  T316: -1

  N316: 2

  T-HOLD: 4000

  T-RETRIEVE: 4000

  T-RESPONSE: 4000

Q931 RX: 2667

Q931 TX: 2097

Q921 RX: 9556

Q921 TX: 9545

Q921 Outstanding: 0 (TEI=0)

Total active-calls:2 global:0

CC records:

Overlap Recv: No

jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

I googled up the ISDN errors;

Cause No. 100 - Invalid information element contents.

This cause indicates that the equipment sending this cause has received and information element which it has implemented; however, one or more of the fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause.

What it means:

Like cause 1 and cause 88, this usually indicates that the ISDN number being dialed is in a format that is not understood by the equipment processing the call. SPIDs will sometimes fail to initialize with a Cause 100, or a call will fail with this cause.

Cause No. 43 - access information discarded.

This cause indicates that the network could not deliver access information to the remote user as requested. i.e., user-to-user information, low layer compatibility, high layer compatibility or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.

So it does appear that something is malformed in the setup request.

jayh
Honored Contributor
Honored Contributor

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

These cause codes are likely related.  The calling number type and plan in the SETUP request from the Adtran are both sent as "unknown".  I'm not sure how to change this in the ISDN settings on the TA900, perhaps someone else can chime in. My suspicion is that it should be "National".  The message in the Asterisk shows it as E.164 which it is actually not.  A true E.164 message would be the plus sign "+" followed by the country code "1" for North America, followed by the ten-digit number.  But, the Asterisk isn't sending that even though it shows E.164.

jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

I found this document that talks about Outgoing Number Conversion and Number Type Templates; https://supportforums.adtran.com/servlet/JiveServlet/previewBody/1304-102-1-1337/Outgoing%20Number%2...

Specifically, this section:


10 digit (256-555-1000)



Comes in as:


L2-Formatted|Ntw2|1| IE - 70 CALLED PARTY # Len=11


L2-Formatted|Ntw2|1| 80 Numb. Type:UNKNOWN


L2-Formatted|Ntw2|1| Numb. Plan:UNKNOWN


L2-Formatted|Ntw2|1| Ph.# 2565551000



Goes out as:


L2-Formatted|Ntw1|1| IE - 70 CALLED PARTY # Len=11


L2-Formatted|Ntw1|1| A1 Numb. Type:NATIONAL


L2-Formatted|Ntw1|1| Numb. Plan:ISDN/Telephony


L2-Formatted|Ntw1|1| Ph.# 2565551000


It *looks* like I need to define an ISDN number template on the 908e to wrap ten digit dialing with the correct type/plan.  Unfortunately I have to do all my troubleshooting after hours but this looks encouraging.

Thanks again, Jay.  

jims
New Contributor III

Re: PSTN PRI issues; inbound CNAME, outbound DID

Jump to solution

OK, I seem to have the outbound DID issue resolved.  The fix was to add ISDN number templates;

View/Delete ISDN Number Templates (TON/NPI)

The following list details the currently configured ISDN Number templates. To delete a template, click on the Delete button next to that template. You can use an existing template as the basis for a new template by clicking on a template row. The form above will be initialized to that template's values.

PrefixDial Plan TemplateType of Number (TON)Numbering Plan Indicator (NPI)
NXX-NXX-XXXXNationalE.164
1-NXX-NXX-XXXXNationalE.164
911NationalE.164
211NationalE.164

09:25:34.313 ISDN.L2_FMT PRI  1  ==============================================

09:25:34.313 ISDN.L2_FMT PRI  1  T Sapi:00 C/R:R Tei:00 INFO Ns:19  Nr:62  P:0

09:25:34.313 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:0083

09:25:34.313 ISDN.L2_FMT PRI  1    M - 05 SETUP      

09:25:34.313 ISDN.L2_FMT PRI  1     IE - 04 BEARER CAPABILITY   Len=3

09:25:34.313 ISDN.L2_FMT PRI  1          80 Xfer Cap.:SPEECH           

09:25:34.313 ISDN.L2_FMT PRI  1          90 Xfer Rate:64k  

09:25:34.313 ISDN.L2_FMT PRI  1          A2 Layer 1:G.711 U-Law   

09:25:34.313 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID          Len=3

09:25:34.313 ISDN.L2_FMT PRI  1          A1 Primary Rate

09:25:34.314 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT

09:25:34.314 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED

09:25:34.314 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO

09:25:34.314 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS

09:25:34.314 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER

09:25:34.314 ISDN.L2_FMT PRI  1          87 Channel:7

09:25:34.314 ISDN.L2_FMT PRI  1     IE - 28 DISPLAY             Len=11

09:25:34.314 ISDN.L2_FMT PRI  1             Office Fax

09:25:34.314 ISDN.L2_FMT PRI  1     IE - 6C CALLING PARTY #     Len=12

09:25:34.314 ISDN.L2_FMT PRI  1          21 Numb. Type:NATIONAL     

09:25:34.314 ISDN.L2_FMT PRI  1             Numb. Plan:E.164         

09:25:34.315 ISDN.L2_FMT PRI  1          80 Presentation:ALLOWED    

09:25:34.315 ISDN.L2_FMT PRI  1             Screening:USER PROVIDED

09:25:34.315 ISDN.L2_FMT PRI  1             Ph.# 1112223333

09:25:34.315 ISDN.L2_FMT PRI  1     IE - 70 CALLED PARTY #      Len=11

09:25:34.315 ISDN.L2_FMT PRI  1          A1 Numb. Type:NATIONAL     

09:25:34.315 ISDN.L2_FMT PRI  1             Numb. Plan:E.164         

09:25:34.315 ISDN.L2_FMT PRI  1             Ph.# 4445556666

09:25:34.346 ISDN.L2_FMT PRI  1  ==============================================

I still get an error after the setup message, but it's a different error and the DID Number is getting set and the call goes through.

09:25:34.346 ISDN.L2_FMT PRI  1  ==============================================

09:25:34.346 ISDN.L2_FMT PRI  1  R Sapi:00 C/R:C Tei:00 INFO Ns:62  Nr:20  P:0

09:25:34.346 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:8083

09:25:34.346 ISDN.L2_FMT PRI  1    M - 7D STATUS     

09:25:34.346 ISDN.L2_FMT PRI  1     IE - 08 CAUSE               Len=2

09:25:34.346 ISDN.L2_FMT PRI  1          82 Location:LN

09:25:34.346 ISDN.L2_FMT PRI  1          E3 Cause:99 (BAD_INFO_ELEM)

09:25:34.346 ISDN.L2_FMT PRI  1     IE - 14 CALL STATE          Len=1

09:25:34.347 ISDN.L2_FMT PRI  1       01

09:25:34.380 ISDN.L2_FMT PRI  1  ==============================================

I'm going to start a new thread on the inbound caller ID name issue so people don't have to scroll through all this.  Thanks again for your help, Jay.

-Jim

View solution in original post

0 Kudos