AA calls routing Incorrectly 1

[telemarv]

I have a customer running a MICS 6.1 with a copper NAM (upgraded to 4.1). They have several analog lines designated as back door for employees to check mail etc. Intermittently calls are routed to wrong extension even thought they swear they entered the correct digits. Adjusting the loss package on these lines has had no effect. Rebooting the NAM and MICS has had no effect.

Anyone experience this before. I've seen this before with crappy cell phones but this is too consistant to be random.

 

[NTL555]

For each of those lines, do you have prime set turned on? Please remove them if you do. Also, make sure touch tone gate is turned off and make sure you ask them how are they calling into the system - ie cell phone, pbx, etc.

 

[luv2ski]

i would go with cell phones everybody has crappy service that they talk on but its so bad that they think just because they can carry on a conversation that all features they need to use touchpad for should work and it doesnt

ONLY 17 WEEKS TILL SKI SEASON STARTS

 

[mroberts]

Just for grins, I would check the TT Gate and make sure it is set to no, like NamLy555 mentioned.

Feature 983, log in
Hit AA then 1 on the dial pad.
TT Gate: NONE

I don't think prime set would have anything to do with it and cell phones are notorious for sending funky digits.

Does it tell them that they have entered an Invalid ext. and to try again?

MRoberts

http://www.a1teletronics.com

 

[telemarv]

Thanks for your responses. Interestingly I hadn't heard of TT gate (another undocumented feature?) what does it do? I'll check its setting.

I changed the line card that these lines are on yesterday. Haven't had any feed back yet.

 

[bkrike]

TElemarv- you changed the line loss- so I am guessing you have LSDS cards? is this correct?
Just trying to correlate between your and NAMLY's problem.

 

[telemarv]

Update: just got word problem still there. these are non global clid cards. TT gate was already set to none.

Further update: now getting complaints of calls on these backdoor lines going directly to random voice mails. I know you're all going to ask... all phones except reception are CFNA/B to voice mail DN, all lines are set to ring at reception except for 3 lines which are back doors.

Both MICS and NAM have been rebooted.

Customer says problems didn't exist before upgrading to 6.1 and 4.1. Previous versions were 2.0 for MICS and 3.0 for NAM.

Aragon HELP... you know which NAM this is.

 

[mroberts]

If you have outside lines ringing on a set (back door lines) then those lines will try to follow the forwarding of that phone.

Therefore, you have the back door lines ringing on sets that are call fowarded on busy to vmail. As soon as they pick up their handset they are creating a busy condition on their phone and the next thing to ring their phone will go to their mailbox. Including those back door lines.

Then that person hangs up and someone else picks up their handset and now the calls will go to that mailbox.

Take Call Forward on busy OFF ALL PHONES THAT HAVE OUTSIDE LINES RINGING ON THEM. Also make sure they aren't fwd no answer in a shorter amount of rings than any AA is picking up.

MRoberts

http://www.a1teletronics.com

 

[Sphoneman]

I would agree with mroberts.

I have seen alot of that type of problem in the forum.
I have NEVER programmed a FB on any phone on any Norstar VM system, only FNA after usually 4 rings. Except for Main Answering positions, usually 6 rings, with the Lines assigned to Ring & Appear(In case of VM locking up).

The users cannot get another call if they needed to and usually spend too much time extracting VM messages.

I teach my customers to use their programmed DND button; this way they can toggle it on & off as many times as necessesary throughout any call & thoughout the day. I also give them an Interrupt button so they can get the call when they just missed answeering. I also tech them to put their phhone in DND when they are gone for the day.


Steve
tele-dataservices.com

 

[telemarv]

Thanks... I know all about CFNA/CFB and their problems with AA. It has been thourghly checked. There is no DN with ringing appearance of these lines. These lines are set to answer is in the NAM with a 2 ring delay to allow for CLID. DRT on these lines are set to NONE. As I said this is an upgraded system from 3.0 to 6.1. Config was backed upped and then upgrade tool used to transfer to new cartridge. Customer says this wasn't happening before the upgrade. I even tried loading the back up copy. I'm getting to the point now of defaultng the whole set up and reprogramming.

 

[luv2ski]

when you upgraded from 3 to 6.1 did you check your services i have had problems with the services being all screwd up after an upgrade routing also.... i did a 3 to 6.1 and it took about 3 to 4 weeks and a couple reboots for all my issues to go away.... take the 4 back door lines and make private to a set ...release... and go back in and then make public then verify vm prog and test

ONLY 17 WEEKS TILL SKI SEASON STARTS

 

[Arr]

Telemarv,

This probably doesn't have anything to do with the problem but.. you did the line renumbering on the NAM that the new 6.1 would need? And for info sake.. what release of telephone sets do you have on the floor? .. what year is the NAM?

Anyone out there know what set emulation a copper NAM uses?

This sounds a little remenicent of a CAP/BLF on Rls 6.1??

PhM

 

[mroberts]

The back door lines are not assigned to ring at any ext??

What line numbers are we talking about? You've made sure that what was line 025 for instance is now programmed in vmail as line 031?
025 - 031
026 - 032
027 - 033
028 - 034
049 - 061
050 - 062
051 - 063
052 - 064
etc.

MRoberts

http://www.a1teletronics.com

 

[telemarv]

All good advise on things to check. Yes the lines in the NAM were changed to reflect the new numbering scheme of 6.1. Back door lines are lines 031, 062 and 063. Sets were changed at the time of upgrade to 7316e's.

Back door lines are set to ring only on DN 275 which is the main DN of the NAM. NAM is on 275 and 276 on 0x16 expansion module.

After reading about weird things happening on B2 channels of ports connect to a NAM in another thread, I'm beginning to wonder if maybe there is something going on the B2 channels of these ports. I'm going to try and move to ports on the main cabinet.

The NAM was orginally a 3.0 upgraded to 4.0 then 4.1.

 

[mroberts]

Oooh, wait a minute.
No lines whatsoever should be assigned in Config programming to ring or appear or anything on the vmail DNs!
They should be assigned in F983 programming. AA, Lines, line: 031, ans: Y, Table:1, Rings: 0.

MRoberts

http://www.a1teletronics.com

 

[Arr]

MR,
I'll bet you've got it there. .. but does the way the NAM communicates with the KSU change or stay the same through an upgrade from 3.0 to 4.1?? I'm trying to compare the interface as if it were a 3rd party vmail.

PhM

 

[mroberts]

Arr,

As far as I know, no they way they relate to each other is the same 3.0 to 4.1.

MRoberts

http://www.a1teletronics.com

 

[Sphoneman]

Third party equipment (VM,IVR) that I've been around, needed ringing assigned but then they usually have some other settings necessary (HF,Auto Ans,FNA,FB) etc needed to complete integration. On a couple systems with digital emulations it was necessary to put a 7310 set on the port first.

Steve
tele-dataservices.com

 

[mroberts]

I used to put AVT (applied voice technologies) vmails on MICS/ CICS and they connected using stn port off the phone system.

They used an NTDIU card (Northern Telecom Digital Interface Unit) to convert the digital ports to analog ports of the vmail. Then you had to fwd no answer/ busy the ports to each other and assign lines directly to those ports.

MRoberts

http://www.a1teletronics.com

 

[Arr]

I was curious as to whether, like an old set, a NAM's connection to the KSU might suffer from the same glitches as a pre rls 17 telephone.

PhM