Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

I can't remove *32 SPN,can't print it and can't add *320 SPN..!!! 1

Status
Not open for further replies.

Optman

Technical User
Apr 14, 2011
528
MA
Hi all

we have problem with adding new SPN (*320)..so when I try to add it, I got Error (ESN073 that means SPN confilct or already exist)..when I try to print this SPN I can't found it on printout file within LD 90.

I can't out it also...please how to resolve this issue

Thanks

Regards


Mostafa OUDDERHEM
 
So true... To bad you don't have trunks on the lab switch (I have the same problem).

I do have a question regarding the * in the SPN. Do you have EMEA software loaded in your lab switch?

I've tried to get the * SPN visible on rls 25.40b, 4.5, 5 and 7 but I do not see the programmed *xxx SPN's. Although the system does see them. After adding I'm unable to add conflicting SPN's (Add *xxx and add *xxxY). And removing is also possible...

Maybe it's region specific...


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
Our lab is a 4021 7.50Q; not even fully patched, w/ North American software. I just don't have any way to test functionality, I can only see if the software accepts my programming. I don't know that I've ever tried "*" in an SPN or DMI on any prior release; I do see a ton of patches on 7.0 regarding numbering plans, etc...

Matthew - Technical Support Engineer Sr.
 
Mouderhem - yes, sorry; I built my DMI wrong. I was using 987 as an example SPN; you could use any 3-digit (or any length) SPN you want.

So 1) build a DMI that deletes 3, and inserts *32; and sets the CTYP appropriately
2) Build a RLI that uses that DMI
3) Build a 3-digit SPN (of your choice that won't conflict) and assign it to that RLI

Now, when you dial your AC1 + SPN + the number you want to call, the PBX will delete the SPN, insert *32, and then dial the rest of the number. Again, none of us know if this will actually work OK once it gets sent out, but ... at least in software, on my PBX, it seems to accept it.

Matthew - Technical Support Engineer Sr.
 
Mouderhem,

Do you have package 104 (OPAO) installed on your switch?

If so, this is my last suggestion. Set OPR to yes on your IAO/OGT DID route and set all the trunk members to CLS DTN.

This is from the Dialing plan NTP

Carrier Access Codes dialing sequences with special characters
The system recognizes two special characters in any dialing sequence. These characters are
the * (star or asterisk) and # (number sign, pound, or octothorpe). The *, when detected in a
dialing sequence, causes a pause in the outpulsing of digits, while the #, when detected in a
dialing sequence, indicates end-of-dialing, that is, no further digits are required to process the
call.
Important:
The asterisk (*) that inserts a three second pause in outpulsing is supported only on analog
and DTI trunks. It is not supported on ISDN trunks. On ISDN trunks, if the OPAO feature is
enabled, the asterisk (*) is outpulsed as a called party digit.




Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
hi all

many thanks for those suggestion:

Mr Nortel4Matt, I have already configure this but the system can't send * to the CO..so on the phone display we see only 32+ number...!

Marc
I will check tomorow for the package 104 (OPAO) and for all 30 trunk members of PRI2 that are DTN ..I will make another test and come back to you with result.

Thanks all
 
Don't forget the OPR on the RDB. That needs to be set to yes.


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
Hi Marc

I have activate OPR on the RDB...the OPAO 104 package is equipped...and then I have change all 30 members of my PRI2 with CLS DTN...but I have the same issue ..we can't send * to the network ISDN...!!
please see the printout of RDB :
>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 23

TYPE RDB
CUST 00
ROUT 23
DES CASA
TKTP DID
NPID_TBL_NUM 0
SAT NO
IDEF NET
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC EURO
CNTY FRA
SBN NO
PNI 00000
NCNA NO
NCRD NO
ISAR NO
CPFXS YES
SDID NO
DAPC NO
INTC NO
MBXR NO
MBXOT NPA
MBXT 0
DSEL VOD
PTYP DCO
CNDP UKWN
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 7505
TCPP NO
PII NO
AUXP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
MFC NO
ICIS YES
OGIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640


PAGE 002

FLH 510
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096

IENB 5
VSS 0
VGD 6
DTD NO
SCDT NO
2 DT NO
DDO NO
DRNG NO
CDR YES
INC YES
LAST YES
QREC YES
OAL YES
AIA YES
OAN YES
OPD YES
NDP EXC 0
CDRX YES
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS YES
MRT 40
MR NO
PANS YES
RACD NO
EQAR NO
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 6
FRL 7 7
OHQ NO
OHQT 00
TTBL 0
ATAN NO
PLEV 2
OPR YES
PRDL NO
EOS NO
DNSZ 0
RCAL NO
MCTS NO
ALRM NO
BTT 30
ACKW NO
ART 0
PECL NO
DCTI 0
TIDY 7505 23


PAGE 003

SGRP 0
ARDN NO
CTBL 0
AACR NO
 
this trace with call (ACOD + *32 + number) DCH MON level 0

DCH 10 UIPE_OMSG CC_SETUP_REQ REF 00000777 CH 60 30 TOD 15:39:57 CK 3C21BF61
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5402 NUM PLAN: E164 TON: UNKNOWN
CALLED #:320661405289 NUM PLAN: E164 TON: UNKNOWN

DCH 10 UIPE_OMSG CC_PROCEED_REQ REF 0000A900 CH 60 1 TOD 15:39:59 CK 3C21CC65

DCH 10 UIPE_OMSG CC_DISC_REQ REF 0000A900 CH 60 1 TOD 15:40:01 CK 3C21D242
CAUSE: #21 - CALL REJECTED

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 0000A900 CH 60 1 TOD 15:40:01 CK 3C21D2CD

ERR4278 0 1020 1000

DCH 10 UIPE_OMSG CC_DISC_REQ REF 00000777 CH 60 30 TOD 15:40:01 CK 3C21DC09
CAUSE: #16 - NORMAL CALL CLEARING

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 00000777 CH 60 30 TOD 15:40:01 CK 3C21DC94


the same call with DCH MON level 2

DCH 10 UIPE_OMSG CC_SETUP_REQ REF 0000077B CH 60 28 TOD 15:42:11 CK 3C25D85D
PRIM HDR: 01 00 01 00 55 00
MSG HDR: 08 02 7B 0E 0E 00
BCAP: 01 0D 13 00 01 10 00 00 23 00 00 00 00 00 00
CHID: 09 09 0D 00 21 00 03 00 01 00 1C
PROGI: 1E 04 03 00 01 83
CLG#: 05 0A 07 00 01 00 04 00 05 04 0A 02
CAD#: 03 12 03 00 01 00 0C 00 03 02 0A 06 06 01 04 0A
05 02 08 09
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

DCH 10 UIPE_OMSG CC_DISC_REQ REF 0000077B CH 60 28 TOD 15:42:19 CK 3C260B6A
PRIM HDR: 01 00 01 00 0D 00
MSG HDR: 08 02 7B 0E 02 00
CAUSE: 07 05 05 00 01 00 10

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 0000077B CH 60 28 TOD 15:42:19 CK 3C260BF3
PRIM HDR: 01 00 01 00 06 00
MSG HDR: 08 02 7B 0E 1A 00


thanks
 
SPN 122

>ld 90
ESN000

MEM AVAIL: (U/P): 98553957 USED U P: 4875054 205930 TOT: 103634941
DISK SPACE NEEDED: 323 KBYTES
REQ prt
CUST 0
FEAT net
TRAN ac2
TYPE spn

SPN 122

SPN 122
FLEN 17
ITOH NO
CLTP NONE
RLI 122
SDRR NONE
ITEI NONE
-------------

RLI 122

>ld 86
ESN000

MEM AVAIL: (U/P): 98553957 USED U P: 4875054 205930 TOT: 103634941
DISK SPACE NEEDED: 323 KBYTES
REQ prt
CUST 0
FEAT rlb
RLI 122

RLI 122
ENTR 0
LTER NO
ROUT 23
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 122
CTBL 0
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0
------------------------
DMI 122

REQ prt
CUST 0
FEAT dgt
DMI 122


DMI 122
DEL 3
ISPN NO
INST *320
CTYP NCHG

------------------

Regards
 
Mr Nortel4Matt

I'm not sure that changing OPR and DID members require to reload DCH..but I can't do this now becaue it is live system...I wait until off hours then I will proceed..

thanks for you great help.

regards

 
Check in LD 57 and see if this number is conflicting with an FFC there.
 
I have print all DNB that starting with (*):

>ld 20

PT0000
REQ: prt
TYPE: dn
TYPE DNB
CUST 0
DN *
DATE
PAGE
DES

DN *0
TYPE FFC
FEAT ELKD

DN *1
TYPE FFC
FEAT ELKA

DN *2
TYPE FFC
FEAT SCPC

DN *4
TYPE FFC
FEAT SSPU

DN *76
TYPE FFC
FEAT CPPO


NACT
 
Check in LD 57 and see if this number is conflicting with an FFC there.
Please explain how an intern dial plan can conflict with an external dial plan?


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
I'm curious - can you make yourself a UNR phone, dial the ACOD of the route, get dial tone, dial *32 + number, and see if it goes thru? Also post a DCH mon 0 trace please of that attempt.

Matthew - Technical Support Engineer Sr.
 
when I dial ACOD + *32 + number...I have the same issue so I see only 32 + number that are passed to CO...star don't pass..

the DCH MON 0 traces:

DCH 10 UIPE_OMSG CC_SETUP_REQ REF 000007BA CH 60 30 TOD 16:44:06 CK 3C974151
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5402 NUM PLAN: E164 TON: UNKNOWN
CALLED #:320661405289 NUM PLAN: E164 TON: UNKNOWN

DTA300 61

DCH 10 UIPE_OMSG CC_DISC_REQ REF 000007BA CH 60 30 TOD 16:44:10 CK 3C976982
CAUSE: #16 - NORMAL CALL CLEARING

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 000007BA CH 60 30 TOD 16:44:10 CK 3C976A0E

Regards
 
Hi all

we have try this PRI line with other IPBX (Nortel BCM450) and we can insert *32 prefix then the blocking CLID feature on outbound calls work fine...!!

Now we have two way to make this feature working on CS1000 system..either check configuration on system to send * character to the CO or discuss with them to changing *32 prefix by another one supporting by CS1000 system...(example 32)...

Thanks
 
one234 (IS/IT--Management) 7 Jul 11 11:33
Quote:
Check in LD 57 and see if this number is conflicting with an FFC there.
Please explain how an intern dial plan can conflict with an external dial plan?

Not saying that one would conflict with the other. What I am trying to explain is why it could not be entered (from the original post)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top