Option 11 NIT Destination 1

[caljud]

Hi folks,

Back in July you guys very helpfully gave me the info to activate a DN enabling caller access to a VSDN menu which Ive set up and can access by dialling 7004. However, I've tried to make 7004 as my NIT 1 destination using LD 15 and, with the switchboard in Night Service, called in on the main number. But my call still follows the old routing which is to a hunt group with 5 extns in. No matter where or what I try/change I can't make my Night Service destination to be 7004. Obviously I've missed something out but, having trawled through the books, can't nail down the change I need to make. Any advice on this would be greatly appreciated. Thanks in advance. Dumb old guy!

 

[KCFLHRC]

When you print the NIT Data does it show 7004 for NIT 1?

 

[Firebird Scrambler]

You might be using two different IDC tables in LD 49 and one would be for day service and the other for night service.

Check in case one of the IDC tables needs a DID number changing.


Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support

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

 

[caljud]

hi kcflhrc,

when I prt nit data in ld21 it shows NIT 1 as 7004 with no timers and nits 2 to 4 with no entries.

hi firebird,

my ld 49 only shows one table

ta

 

[KCFLHRC]

Is 7004 a phantom or a dummy acd que?

 

[yyrkroon]

Easy enough to test.

Onsite - dial 0, if the console is logged out - NIT1 will kick in.

If you get different result dialing internal vs external, then look at the IDC table or enable DCH messaging if the call is coming in on PRI.

 

[caljud]

7004 is a dummy acd que

 

[yyrkroon]

doesn't matter how 7004 is built, if it's set as NIT1, when the console is in nite, caller are going to be forward to 7004 and does exactly what 7004 is programmed to do.

 

[KCFLHRC]

What is the hunt group DN ?

 

[StanleySteamer]

Do you have analog trunks? You may have a NITE entry on the trunk TN's that is overriding the CDB entry.

 

[caljud]

Hi KCFLHRC
7004 is a dummy ACD queue with ACDN set as 7004, MAXP set to 1 and NCFW set to 7000 (mail access). When I dial 7004 internally the mail system answers and performs all the functionality I have set up with regard to selection routing etc. I have set 7004 to be the NIT 1 setting using LD15 but when I call in on the main DDI number ending 341 the call follows the old routing to a hunt group containing 5 extensions. My LD 49 IDC table shows that DDI 341 only has one way out which is to "0". When the switchboard is set to NIT and I dial 0 internally my call goes to the mail system which says "your session cannot be completed at this time". Also, although my LD21 print of NIT shows 4 selections possible (NIT 1 being 7004) the switchboard only shows NIT when set and the operator onsite has only ever seen this display - never an invitation to set NIT2... etc.

Any clues as to where to look and under which command would be greatly appreciated.

 

[KCFLHRC]

The problem is it is carrying the originally dialed # into the voice mail, which is 0. Probably the easiest thing to do is to make a night IDC table and send 341 to 7004. I'm not sure how it is getting to the hunt group. It may be that there is already a night IDC table doing this. Look in the route under DCNO and NDNO and see if they are pointing to different IDC tables.

 

[StanleySteamer]

If you put 0 in your VSDN table with the same treatment as 7004 it may fix your internal calls when dialing 0. But I doubt that will resolve the problem with external calls.

You might be able to find what's going on by setting up an LD 80 ENTC for the first TN in the hunt group.

As KCFLHRC suggests, we aren't seeing the whole picture. It would be much easier for people here if you posted the actual switch data so we can see it:
LD 21 CDB (all of it)
LD 21 RDB for incoming routes
LD 49 IDC (all)

 

[caljud]

Hi guys,
Re : the ongoing saga - thanks to all for your current input. However, having a weekend away from the issues has given me an idea which, from this morning's delving, has, I think, given me a clue as to whats going on and for which I would appreciate some thoughts.

Currently, when I list LD49, I only get 1 table showing the last 3 digits of the incoming dialled number allied against the translation currently programmed i.e. 341 is sent to 0...etc...etc . This suggested to me that cos the systems pretty old with regard to s/w level, I do not have a Night DDI routing available. When the system is set to NIGHT (not NIT 1, Nit 2 etc which are not given as an option on the switchboard but can be programmed under LD15) incoming calls on xxx341 are sent to a hunt group with PLDN 441 containing 5 extensions. I think this means that when in NIGHT the system is treating the call as a normal analog trunk and not as a ddi trunk. Hence me making NIT 1 to be 7004 has no effect.

Therefore, would anyone be good enough to list me the commands I need to do the following:

- List/print the current trunk listing to include ring maps etc.
- If the above theory is correct how to change the Night ring map to be 7004 instead of hg441.
- Any other things to do so that I don't make a mess of things if I change them.

Thanks to all in advance

Really old dumb guy!

 

[caljud]

Hi guys,

Just a quick note to all who gave input. I found the fix this morning. The system here is so old it wouldn't let me use oveerlays 14 and 16 so I couldn't do anything with rdb's etc. So what I did was, as suggested above, put 0 in my VSDN table with same routing as 7004. I then put 0 as the only member in the Night Hunt Group. Tried all permutations of incoming calls to the main number and all CCR routings in the Mail - all worked great when system in Night Service. Day service follows original routings so no prob there.

Again thanks to all and have a good weekend.

 

[KCFLHRC]

Ld 14 and 16 have been around since dirt