[Home]

Summary:ASTERISK-06595: callerid= in zapata.conf not used for calls coming in on that PRI
Reporter:Nabeel Jafferali (nabeelj)Labels:
Date Opened:2006-03-22 09:28:24.000-0600Date Closed:2011-06-07 14:07:54
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hello. We have a dual-T1 card in our Asterisk server.

The first port is connected to the telco (using national and pri_cpe) and the second port is connected to a legacy PBX (using 5ess and pri_net). The legacy PBX is unable to set caller ID, so before the group and channel statements for that PRI, I have a callerid="Name" <4169671111> statement.

However, when calls are received from the legacy PBX, Asterisk does not replace the caller ID info with the info I set in zapata.conf.

I even tried putting a usecallerid=no, thinking Asterisk may have been using the blank caller ID being sent by the PBX and would now ignore it, but that did not fix it.

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

[channels]
cidstart=ring
usecallingpres=yes
echocancel=yes
echocancelwhenbridged=no
rxgain=-1
txgain=-1

context=pri-in
switchtype=national
pridialplan=national
prilocaldiaplan=national
signalling=pri_cpe
group=1
channel=1-23

;usecallerid=no
callerid="Name" <4169671111>
accountcode=100
context=pbx-in
switchtype=5ess
signalling=pri_net
group=2
channel=25-47
Comments:By: twisted (twisted) 2006-03-22 10:26:00.000-0600

You listed your version as 1.2.0.  can you update your version to a more recent version and try again?

By: Clod Patry (junky) 2006-04-23 14:16:18

Lacks of interest here.
Feel free to re-open, if needed.