PBX Info :: Your Free PBX, PABX and Telephone Information Resource - View Single Post - Forcing Outbound CLID
View Single Post
Old 11-25-2007, 02:22 PM   #4 (permalink)
EricP
Junior Member

Activity Longevity
0/20 14/20
Today Posts
0/0 sssssss11
Rep Power: 5EricP is on a distinguished road
Here is how you do it on a Regular T1.

TABLE: CXGRP
>pos 682
682
Y 7144829100
N
N
N
N
N
N
( RMR ) ( RMT )$
>cha
SPB: Y
>
BILLNO:
>
CTD: N
>
FCTDNTER: N
>
FCTDNTRA: N
>
FCTDINT: N
>
EWATS: N
>
EWATSI: N
>
PXOPTION: RMR
>
PXOPTION: RMT

PXOPTION:
>cnum
CLGNUM:
>
BLKPRES: N
>
PXOPTION:
>cnam
CLGNAME:
>Century_21

Here is how you do it on a PRI

Adding caller id to a pri
Ni2 allows the cust to outpulse ext #’s, dms 100 will always use the btn. Table ltdata is the protocol has ni2 can override what the customer sends us. But there must be these following touples. For outbound caller id outbound the ltdata needs to be serv always always with the btn updated in lidb for the customer name.


Table Ltdata
>pos pra 929 serv
PRA 929 SERV
SERV Y N SCREENED ALWAYS (BNS SBN) $
>up
PRA 929 DN
DN 503 111 1111 $ THIS MUST BE HERE TO OVERIDE THE CUSTOMER

IF THAT DOES NOT WORK ADD THIS
>add pra 929 cli cli $

>pos ISDN1 203 SERV
ISDN1 203 SERV
SERV Y Y SCREENED ALWAYS (BNS SBN) $
>cha
DATATYPE: SERV
>
AUDTRMT: Y
>n
CGNREQD: Y
>
CGNDELV: SCREENED
>always
CDNDELV: ALWAYS
>
OPTION: BNS
>
BNS: SBN
>
OPTION:
>tcap_cnam
CNAM_SUSP:
>n
OPTION:
>$
TUPLE TO BE CHANGED:
ISDN1 203 SERV
SERV N Y ALWAYS ALWAYS (BNS SBN) (TCAP_CNAM N) $
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.
>y
TUPLE CHANGED
WRITTEN TO JOURNAL FILE AS JF NUMBER 966
EricP is offline   sendpm.gif Reply With Quote