asterisk users - Oct 2008 - hex b1 in CallerID sent by Asterisk On PRI

I'm trying to send CallerID info to a MetaSwitch system over a PRI. The
MetaSwitch gets the info exactly as it is sent by Asterisk, but I think
it might be having trouble with the Hexadecimal b1 that is being sent
just before the first character of the CallerID Name.

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?

I've pasted a portion of the PRI debug trace below.

Thanks for your help.

Bob

-- Making new call for cr 32985
> Protocol Discriminator: Q.931 (8)  len=55
> Call Ref: len= 2 (reference 217/0xD9) (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 a9 83 97]
> Channel ID (len= 5) [ Ext: 1  IntID: Implicit  PRI  Spare: 0
Exclusive  Dchan: 0
>                        ChanSel: As indicated in following octets
>                       Ext: 1  Coding: 0  Number Specified  Channel
Type: 3
>                       Ext: 1  Channel: 23 ]
> [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 0a b1 54 65 73 74 20 4e 61 6d 65]
> Display (len=10) Charset: 31 [ Test Name ]
> [6c 0c 21 80 34 30 33 35 35 35 31 32 31 32]
> Calling Number (len=14) [ Ext: 0  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>                           Presentation: Presentation permitted, user
number not screened (0)  '4035551212' ]

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20081021/e6274590/attachment.htm

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