[Home]

Summary:DAHLIN-00128: Asterisk not sending CNAM properly in PRI Facility IE data
Reporter:Ernie Dunbar (ernied)Labels:
Date Opened:2009-07-21 12:08:45Date Closed:2012-04-03 17:25:28
Priority:MinorRegression?No
Status:Closed/CompleteComponents:dahdi (the module)
Versions:2.1.0.3 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) PRI_calltrap.txt
Description:We informed our PRI provider that outgoing callerid doesn't include CNAM information, but does include CNUM. They did a calltrap (attached) and their results are that Asterisk sends the CNAM using the "Display" information element in the Standard Facility IE information.

We're pretty sure we've done all we can with our DAHDI configuration, as chan_dahdi.conf uses "switchtype=5ess", "signalling=pri_cpe", and "facilityenable=yes", plus our calls to the PRI actually work with only this minor issue.

Searching issues.asterisk.org for similar issues with Standard Facility IE produces results that say this issue is already fixed, but this may be a problem specific to our PRI provider (Group Telecom, now owned by Bell Canada) or our PRI switchtype.

****** ADDITIONAL INFORMATION ******

We have:
Gentoo Linux 2008.0 (kernel 2.6.27-gentoo-r7)
Asterisk 1.4.23.1 (newer versions crash on our system!)
Dahdi-linux 2.1.0.3
Dahdi-tools 2.1.0.2
libpri-1.4.9

Our PRI provider (Group Telecom/Bell Canada) has:
Lucent 5ess switch
Using ESF, B8ZS
PRI type is NI2

Our chan_dahdi.conf is:

[channels]
usecallerid=yes
facilityenable=yes
hidecallerid=no
callwaitingcallerid=yes
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
echocancelwhenbridged=no
immediate=no
group=1
signalling=pri_cpe
;switchtype=national
switchtype=5ess
context=local
channel=>1-23
rxgain=0
txgain=0
busydetect=yes
busycount=5
Comments:By: Shaun Ruffell (sruffell) 2012-04-03 17:25:28.254-0500

Closing this old issue. Please reopen if you still have this problem with current versions of libpri. This is most likely an issue in libpri anyway, and not in dahdi-linux.