![]() | |
| |||||||||||||||
| |||||||||||||||
| Mitel Ask Questions and Find Answers on Mitel Systems: |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Moderator ![]() ![]() acejavelin is a high-tech, heavy metal redneck!
Location: North Dakota Rep Power: 2 ![]() | LDN to Ring Group to Call Director on 3300 OK, I know I have done this before, but this is not working correctly, give me some ideas here on what I am missing. Some general info: - Call comes in on PRI DID trunk with DNIS 2500 - 2500 is a System Speed Call Entry to 301 - 301 is a LDN assignment on 5550 IP Console - 311 is a Ring Group that overflows to "197" <see below> - 197 is Call Director Mailbox in Nupoint 3.0 (MAS) - 300 is the Nupoint hunt group number What I am trying to do is this: The call rings the LDN 301 appearance for 30 seconds, then reroutes to ring group 311. <= This works fine Ring group 311 Rings 6 phones <= This works fine After 20 seconds and overflows to "197". <= This is where the fun begins In this setup "197" ALWAYS gives me the message "Welcome to the message center..." no matter how I setup "197" on the 3300 side. It can be a nametag huntgroup that is rerouted to 300, it can be an extension that is rerouted always to 300, and I have tried an extension that is just using Call Forward Always to 300 and no rerouting; at the same time, just dialing "197" from a phone (or pointing another DID directly to 197) gives me the Call Director menu and options I expect no matter which way I setup 197. Another piece of info, if I add 301 as a alternate extension in mailbox 197 on the Nupoint it works. I am using this as a kludge for the moment to get by, but I use a similar setup at night but a different Call Director mailbox, so I can't leave it like this. I know I have done this before more than once and it has worked fine. What could I be doing wrong or what did I miss or add by accident? __________________ Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost. This is Telephony’s First Law of Equivalent Exchange. Last edited by acejavelin; June 16th, 2009 at 11:04 PM. Reason: added detail/corrected info | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Senior Member ![]()
Rep Power: 5 ![]() | ok heres what I think, the 3300 tags the call with the primary destination point (301) as this call interflows through the system it is still tagged with its destination 301 so when it goes to Nu Point it trys to send it to a mailbox that contains ext 301 (this is why it works when you add it as a alternate ext number.) What I would try is sending speedcall 2500 to 197 (Hunt group) and call reroute always to 301 and then let it flow through to nu point. Hope this helps | ||||||||
| | |
| | #3 (permalink) | |||||||||
| Moderator ![]() ![]() acejavelin is a high-tech, heavy metal redneck!
Location: North Dakota Rep Power: 2 ![]() | Quote:
This would cover me for Day and Night 1 modes, Night 1 is almost identical to day except 301 reroutes immediately 311. They use this when no operator is present during the day. But in Night 2 mode, which they use when they are closed, I am trying to to do the same as Night 1 except go to Ring Group 312 and overflow to 198 for a different Call Director mailbox. And to confuse it even more, I also have a second number of LDN of 302 that has similar call flow as above, except uses different ring groups (321&322) but still uses the same Call Director mailboxes. Gee, I wish the 3300 had a D/N1/N2 DID routing table like the 200ICP, it would make life so much simpler... __________________ Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost. This is Telephony’s First Law of Equivalent Exchange. | |||||||||
| | |
| | #4 (permalink) | ||||||||
| Moderator ![]() ![]() acejavelin is a high-tech, heavy metal redneck!
Location: North Dakota Rep Power: 2 ![]() | Well, looks like this is mute problem. According to tech support it just will not function this way. We are going to activate the embedded voicemail and use it to handle the overflow/night auto attendant functions and let the Nupoint do all the voicemail stuff. __________________ Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost. This is Telephony’s First Law of Equivalent Exchange. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Local and remote call forwarding for a ring group | jzawacki | Asterisk | 0 | May 22nd, 2009 09:49 AM |
| 3300 Ring Group Remote Member | backitup | Mitel | 3 | February 26th, 2009 10:56 AM |
| Integrated Call Director | WhereWolf | Meridian Systems | 1 | December 1st, 2008 09:05 AM |
| 3300 Hunt Group w/Voicemail | syntaxvw | Mitel | 2 | April 1st, 2008 08:36 AM |
| 3300 Flash on call in a Pickup Group | Rat Catcher | Mitel | 2 | February 20th, 2007 12:25 PM |