DAPC on DPNSS yes or no ? 1

[SL1M1]

Guys, come across the Plug in 72 on the list and was able to 'Enable' as confirmed in LD 22 ISSP (Bottom of report) do I need to sysload or INI to complete the process as I still can't see DAPC/TABL prompts in the route config.

I have my doubts if this even can be done on DPNSS but thought to put it out there...Our friend FireBird might want to advise as my guess is the best option would be to get the customer to request the Mobile op to add the AC1 code to the Mobile CLID's ?

I have this set up on others but there ISDN etc

Cheers Guys!!

 

[Firebird Scrambler]

Hi SL1M1. I'm back home now. To add the AC1/AC2 via DASS or DPNSS, you need to go to LD 15 under NET and find DASC.

i.e.

ORION USERS REQUIRING TO SEE AC1 CODE ON SET DISPLAY
dasc in cdb

IF ACCESS CODE IE 9 REQUIRES TO BE
DISPLAYED IN FRONT OF I/C CALLING
LINE ID " ON DISPLAY OF TELE "
ORION USERS REQUIRING TO SEE AC1 CODE ON SET DISPLAY
PROMPT DASC IN LD 15 DOES THE JOB
AC1 HAS TO BE CHANGED THEN CHANGED
BACK AFTER DASC SET
THIS CAN BE USED ON ORION TELES
WHICH STORE CLI ON CALLERS LIST
*TO REMOVE DASC USE CHG AND PUT IN THE ATDN IE. IF 0 THEN USE 0

I hope it helps?.

####################################################

CLID in Mail does not work if DASC configured?

If DASC is configured to match AC1 so that the CLID of an incoming call is prefixed with a 9 on digital sets' displays, messages left in mail will fail to register the CLID and will state "message from an unknown number".
With DASC configured, the telephone sets display 9--01712309900 (eg). A trace of the Mail AML messaging shows 9EE01712309900 sent into mail as the CLID.

Nortel say this is design intent, so choose one or the other feature, but not both.
26/10/2000

##########################################################

CS1000 IP sets: how to add the 9 prefix to the CLID of incoming calls

CS1000 IP sets: i2002, i2004, 1120, 1140, 1150 etc

Incoming DDI calls on DASS2 delivered to an IP set do not have the pstn access code prefixed to the caller's CLID - normally 9 (AC1) - and so in order to use the Redial facility the user has to edit the number in the Callers List by adding the 9 before dialling.

The 9 can be automatically added by configuring DASC in the NET_DATA with the value 9.
Note: if AC1 is already 9 in the ESN, you will have to change AC1 to something else temporarily so that DASC can be set to 9, then change AC1 back to 9 afterwards.
To remove the DASC value, enter the Attendant DN against the DASC prompt.

Further gotchas:
1) With DASC set to 9, incoming DDI calls will show 9-- in front of the CLID. In this case no match will be found between the displayed CLID and any stored entry in the user's Personal Directory. To get rid of the --, fit mplr15900.
2) Even with mplr15900 fitted, if the DASS route data block has DNIS set to yes, no match will be made with the Personal Directory.
3) If the call does not route directly to the IP set but goes through a CDN, for example, the Callers List will not be populated with details of the call.







All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[SL1M1]

Hi there FireBird, I'll look into this in detail on my return...This hopeully looks to be the resolution

You see my AC1 is '0' which I've introduced on incoming calls using DAPC on other 'ISDN' routes relating to TABL X built in CDB but never been able to find a fix on DPNSS or indeed DASS, for user redial's with leading AC1 digit thereby digits outgoing SPN's capturing and routing those calls accordingly

As I say, came across your previous helpful posts especially regarding 'PlugIn's which enabling '72' in PDT referring to DPNSS DAPC, I can see and confirm this in
LD 22 ISSP but nothing changed in IDA RDB...I must admit overlooked the NET in LD 15 which I guess as you've suggested is also relevant for DPNSS working routes

Cheers my friend and I'll report back on the outcome

 

[Firebird Scrambler]

No worries SL1M1. You can contact me off line if you need any more help.

Take care

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[SL1M1]

Hi again FireBird, carried out that re-config remoteley OOH due to the AC1 temp change to allow the DAPC to be changed in the NET DATA without users being effected

Test calls this morning now on DPNSS CLID on mainly 3904/3902's displays have 0-077xxxxxx when selecting redial it has now the desired output 0077xxxxx and the SPN's take care of the routing down the Orange DPNSS Link

Many Thanks for your time and support hopefully this post/solution can be of use for others regarding DPNSS CLID
my search for your help direct was due to your expertise in Cellular/Mobile/NortelConfig work. Ideally though it would have been nice for the Customer to persuade Orange (MobileOp) to insert for us, but I guess that would have cost implications

Cheers and have a good week my Friend !!

 

[Firebird Scrambler]

Great news to hear that it worked OK!.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.