[asterisk-users] hex b1 in CallerID sent by Asterisk On PRI

[Bob Pierce]

On Tue, 2008-10-21 at 13:56 -0500, Bob Pierce wrote:
> Does anyone know what the significance is of the b1 being sent here?
> 
> Or, is there a way to make Asterisk not send the b1 character as a
> test?

As an update to this, I noticed the following lines in libpri.h near
line 236:

/* Network Specific Facilities (AT&T) */
#define PRI_NSF_NONE                   -1
#define PRI_NSF_SID_PREFERRED          0xB1
#define PRI_NSF_ANI_PREFERRED          0xB2


So, I've tried specifying nsf=none in zapata.conf, but we still see
the b1 preceding the caller name in the pri trace. However, I only did a
'reload chan_zap.so' since this is a production system. Should that have
changed the nsf settings for this span?

My current zapata.conf is pasted below if that helps...

Bob


[trunkgroups]

[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1

immediate=no

;Sangoma A104 port 1 [slot:4 bus:13 span:1] <wanpipe1>
switchtype=national
context=inbound
group=1
signalling=pri_cpe
channel =>1-23

;Sangoma A104 port 2 [slot:4 bus:13 span:2] <wanpipe2>
context=stations
group=0
signalling=fxo_ks
channel => 25-48

;Sangoma A104 port 3 [slot:4 bus:13 span:3] <wanpipe3>
switchtype=national
nsf=none
context=metaswitch
group=2
signalling=pri_cpe
channel =>49-71