Hi, thanks for the reply. Yes, its in the LDN (form 8). To further complicate things they are using key 0 for 2 references. One is the "Monday" line and the other is an 800 number we have that use to service "Monday".
I talked with the receptionist and she said not to worry about it as its sounding like its getting messy.
But if its something simple i'd still be curious as to how to change it. There is one key slot left (number 1), but I suspect that has some "key" use (pun intended .
Number 1 (F1) on the console is recall and is not programmable in form 8.
Your statement about using "Key 0 for 2 refernces" does not compute. I'm sure you knew what you meant but I sure don't.
Is the DID you mentioned earlier programmed as one of the DN's on the console? If yes, change the name to what you think is appropriate. If not, what is that DN programmed as and more specifically what tenant. Cross ref the tenant and check the form 19 routing for DID's into this tenant.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Hi, key 0 is labled "MONDAY" but in the comments field the VAR put in MONDAY + 1800.
This is a legacy thing from a time gone by. The collections gal would like the console to read "COLLECTIONS" if someone uses the 1800 line (attached to key 0)
But the MONDAY line is also part of key 0, so i can't rename it to "COLLECTIONS" otherwise the receptionists would get confused.
I see the logic from the original programmers standpoint as that 1800 num was part of "MONDAY" but now its not.
Without extra key slots I can't really do much for her.
I programed form 55 ext 7777 to be picked up by a phantom ext with has a menu tree set up.
Because to separate divisions were using the same number it made sense to have Press 1 for Annemarie and press 2 for Margaret so I don't know what the original termination number was.
As a side note, when the system was having major issues last week, if I took the first T1 span LAN cable and plugged it into the T1 port of the framer module, all the "480-xxxx" dids would ring the system.
But, if I took the T1 span LAN cable and plugged it into T2 of the framer card callers would either get a busy signal or unable to complete call error.
Is it possible because the second span does not have that *7 in the X column?
N = Digits expected = 7
M = Digits Absorbed = 3
X = Digits added = *7
*7 will be programmed in form 2 as the DID Translation Table prefix digits.
The remaining 4 digits (7 expected, 3 absorbed) are optionally programmed in for 55. The *7 is stripped when form 55 is engaged. If the remaining 4 digits match in form 55 then routing is determined for Day, Night1, and Night2 as defined in form 55. If the 4 digits do not match any entries in form 55 then the digits are processed "as is".
The second span does not have the *7 as you have observed. What this means is that any special routing programmed in form 55 programming is ignored and ALL DID's are processed based on their remaining 4 digits.
When you say I have programmed 7777 ...., does this mean you have now put in place a solution to your problem?
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Interesting info, I was wondering why when the lan cable was plugged into the 2nd port of the framer module all the 480 DIDs were getting tossed.
When our system tanked, if I had programmed the second t1 span with the *7 then that would have allowed the 480 DIDs to have gone to form 55 and have routed properly?
Yes, I chose this as the solutions: I set 7777 in form 55 to ring 371 (a phantom extentsion). In form 50, I told 371 to be a Menu Tree and programmed the operator (0), 744(1) and 126(2).
This now solves the problem of the switch board having to answer it and allow the caller to choose from the 2 depts. If they get totally lost then and they hit 0, it will call the switch board, but at that stage of the game, it doesn't matter how the switch board answers it as the caller already needs help haha.
This was a cool convo, thanks for taking the time. I learned a few new tricks that I didn't know about.
Cool, Glad to help. The solution I was going to suggest involved naming the phantom appropriately and forwarding it to #411. The result would have been mostly the same as the original scenario but the call would have come in on the same key and the display would have read "Forwarded from NAME".
P.S. You can program the 2nd span trunks with the *7 as long as the trunk is idle.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.