• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1259
  • Last Modified:

Asterisk PRI Outbound CallerID not working

I am running two asterisk servers that have 8x PRI's each.  Some of them are with TelePacific, and the rest of them are from some other company.  (The other company is not the issue.)

On the other "company" PRI's, The CallerID number shows up perfectly on the outbound call.  On the other, I can't seem to get it to work at all. I am going to attach the PRI INTENSE log for a outbound call on a problem channel.  I am set to use NI2, pri_cpe.  Any help would appreciated!

*  Please note that I added ???? for the last 4 in the code snippet for censorship, it is 4 digits numerical.
 
[root@apexfront2 asterisk]# asterisk -r
Asterisk 1.6.2.9, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 1.6.2.9 currently running on apexfront2 (pid = 17550)
Verbosity is at least 3
  == Manager 'cmdadminnew' logged on from 192.168.0.133
    -- Executing [apexoutbound@apexdial:1] NoOp("Local/apexoutbound@apexdial-1cbd;2", "ApexVox requesting outbound") in new stack
    -- Executing [apexoutbound@apexdial:2] NoOp("Local/apexoutbound@apexdial-1cbd;2", "18008520411") in new stack
    -- Executing [apexoutbound@apexdial:3] NoOp("Local/apexoutbound@apexdial-1cbd;2", "ACA") in new stack
    -- Executing [apexoutbound@apexdial:4] Set("Local/apexoutbound@apexdial-1cbd;2", "CALLERID(num)=1800852????") in new stack
    -- Executing [apexoutbound@apexdial:5] Set("Local/apexoutbound@apexdial-1cbd;2", "CALLERID(name)=ACA") in new stack
    -- Executing [apexoutbound@apexdial:7] Dial("Local/apexoutbound@apexdial-1cbd;2", "DAHDI/37/e17025052773,55") in new stack
-- Making new call for cref 32769
    -- Requested transfer capability: 0x00 - SPEECH

> DL-DATA request
> Protocol Discriminator: Q.931 (8)  len=54
> TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
> Message Type: SETUP (5)
TEI=0 Transmitting N(S)=0, window is open V(A)=0 K=7

> TEI: 0 State 7(Multi-frame established)
> V(A)=0, V(S)=0, V(R)=0
> K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
> T200_id=0, N200=3, T203_id=1
> [ 00 01 00 00 08 02 00 01 05 04 03 80 90 a2 18 03 a1 83 8d 1e 02 80 83 28 04 b1 41 43 41 6c 0d 21 81 31 38 30 30 38 35 32 30 34 31 31 70 0c 81 31 37 30 32 35 30 35 32 37 37 33 ]
> Informational frame:
> SAPI: 00  C/R: 0 EA: 0
>  TEI: 000        EA: 1
> N(S): 000   0: 0
> N(R): 000   P: 0
> 54 bytes of data
> Protocol Discriminator: Q.931 (8)  len=54
> TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
> Message Type: SETUP (5)
> [04 03 80 90 a2]
> Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer capability: Speech (0)
>                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)
>                                User information layer 1: u-Law (34)
> [18 03 a1 83 8d]
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0  Preferred  Dchan: 0
>                       ChanSel: As indicated in following octets
>                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
>                       Ext: 1  Channel: 13 Type: CPE]
> [1e 02 80 83]
> Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  0: 0  Location: User (0)
>                               Ext: 1  Progress Description: Calling equipment is non-ISDN. (3) ]
> [28 04 b1 41 43 41]
> Display (len= 4) Charset: 31 [ ACA ]
> [6c 0d 21 81 31 38 30 30 38 35 32 30 34 31 31]
> 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 passed network screening (1)  '1800852????' ]
> [70 0c 81 31 37 30 32 35 30 35 32 37 37 33]
> Called Number (len=14) [ Ext: 1  TON: Unknown Number Type (0)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)  '17025052773' ]
-- Stopping T203 timer
-- Starting T200 timer
q931.c:4959 q931_setup: Call 32769 enters state 1 (Call Initiated).  Hold state: Idle
    -- Called 37/e17025052773

< TEI: 0 State 7(Multi-frame established)
< V(A)=0, V(S)=1, V(R)=0
< K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
< T200_id=1, N200=3, T203_id=0
< [ 00 01 01 02 ]
< Supervisory frame:
< SAPI: 00  C/R: 0 EA: 0
<  TEI: 000        EA: 1
< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 001 P/F: 0
< 0 bytes of data
-- Got ACK for N(S)=0 to (but not including) N(S)=1
-- ACKing N(S)=0, txqueue head is N(S)=-1 (-1 is empty, -2 is not transmitted)
-- Stopping T200 timer
-- Starting T203 timer
Done handling message for SAPI/TEI=0/0

< TEI: 0 State 7(Multi-frame established)
< V(A)=1, V(S)=1, V(R)=0
< K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
< T200_id=0, N200=3, T203_id=1
< [ 02 01 00 02 08 02 80 01 02 18 03 a9 83 8d ]
< Informational frame:
< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1
< N(S): 000   0: 0
< N(R): 001   P: 0
< 10 bytes of data
< Protocol Discriminator: Q.931 (8)  len=10
< TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent to originator)
< Message Type: CALL PROCEEDING (2)
< [18 03 a9 83 8d]
< Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0  Exclusive  Dchan: 0
<                       ChanSel: As indicated in following octets
<                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
<                       Ext: 1  Channel: 13 Type: CPE]
Received message for call 0x8b57880 on 0x8b32b08 TEI/SAPI 0/0, call->pri is 0x8b32b08 TEI/SAPI 0/0
-- Processing IE 24 (cs0, Channel Identification)
q931.c:6998 post_handle_q931_message: Call 32769 enters state 3 (Outgoing Call Proceeding).  Hold state: Idle
-- Got ACK for N(S)=1 to (but not including) N(S)=1
-- T200 requested to stop when not started
T203 requested to start without stopping first
-- Starting T203 timer

> TEI: 0 State 7(Multi-frame established)
> V(A)=1, V(S)=1, V(R)=1
> K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
> T200_id=0, N200=3, T203_id=1
> [ 02 01 01 02 ]
> Supervisory frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 001 P/F: 0
> 0 bytes of data
Done handling message for SAPI/TEI=0/0
    -- DAHDI/37-1 is proceeding passing it to Local/apexoutbound@apexdial-1cbd;2

< TEI: 0 State 7(Multi-frame established)
< V(A)=1, V(S)=1, V(R)=1
< K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
< T200_id=0, N200=3, T203_id=1
< [ 02 01 02 02 08 02 80 01 03 1e 02 84 88 ]
< Informational frame:
< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1
< N(S): 001   0: 0
< N(R): 001   P: 0
< 9 bytes of data
< Protocol Discriminator: Q.931 (8)  len=9
< TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent to originator)
< Message Type: PROGRESS (3)
< [1e 02 84 88]
< Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  0: 0  Location: Public network serving the remote user (4)
<                               Ext: 1  Progress Description: Inband information or appropriate pattern now available. (8) ]
Received message for call 0x8b57880 on 0x8b32b08 TEI/SAPI 0/0, call->pri is 0x8b32b08 TEI/SAPI 0/0
-- Processing IE 30 (cs0, Progress Indicator)
-- Got ACK for N(S)=1 to (but not including) N(S)=1
-- T200 requested to stop when not started
T203 requested to start without stopping first
-- Starting T203 timer

> TEI: 0 State 7(Multi-frame established)
> V(A)=1, V(S)=1, V(R)=2
> K=7, RC=0, l3initiated=0, reject_except=0, ack_pend=0
> T200_id=0, N200=3, T203_id=1
> [ 02 01 01 04 ]
> Supervisory frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 002 P/F: 0
> 0 bytes of data
Done handling message for SAPI/TEI=0/0
    -- DAHDI/37-1 is making progress passing it to Local/apexoutbound@apexdial-1cbd;2
    -- DAHDI/37-1 is making progress passing it to Local/apexoutbound@apexdial-1cbd;2
apexfront2*CLI> exit
[root@apexfront2 asterisk]#

Open in new window

0
Iamtehbest
Asked:
Iamtehbest
  • 2
  • 2
1 Solution
 
naulivCommented:
Hello,

Looks like your dialplan for outbound dialing on Telepacific is:
    Set(CALLERID(num))="1800852????"
    Set(CALLERID(name))="ACA"
    Dial(DAHDI/37/e17025052773,55)

Can you confirm, and let us know the actual behavior when you dial out ? (are you getting always the same callerID no matter what; or no callerID at all, or something random ?).

Thanks!
0
 
IamtehbestAuthor Commented:
Sorry, I've been bangin my head on this problem for months.  I had to get to the bottom of it tonight. . . And I finally figured it out.  The symptom was that no matter what I filled the Caller ID information with, the receiving party never gets the caller ID on these PRI's.  I tried all the the prefixing of dialstrings to see if the off chance that it would work.  Nothing.

Then I posted on here in desperation.  After taking a bio, and realizing that if I did indeed tried every dialplan prefix then somethings gotta be wrong with the callerid that I am filling in.  My very first attempt at fixing the caller id (although theres nothing wrong with what I put in there in the first place) was to change the "1800" to "800" of the CallerID Num.  

And it works now,  CallerID Name doesn't.. but atleast the number is in there.

You wouldn't happen to know why the Name doesnt work eh?

To answer your question, just incase its relevant to the name: The symptom was I was not getting any caller id name or number.  Now I get any number I plug into the CallerID(num).  Name still doesn't work.
0
 
naulivCommented:
Glad your calledID nums works!

CallerID name are not "passed" by carriers on outbound calls... it is always the receiving party's carrier that is doing a "look up" in one of the major databases to bring the name up. See this link for more info: http://en.wikipedia.org/wiki/LIDB


0
 
IamtehbestAuthor Commented:
It now makes sense.  THanks.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now