gntsfan8690
Vendor
I saw one other post re: this, but would like to present my situation. With this being so new, not sure whose had a chance to mess with it.
After cutting over a customer to their 10.1 Server Edition from a Nortel CS1K, we found out one department was using what sounded like an MADN button(s) to receive what we'd treat as a collective hunt group call, and also to call out occasionally using the department DID as the caller ID. As of now when users call out they will send their own DID, and I have main # of their office coming into a collective call waiting hunt group that has a group mailbox covering calls. I'm kind of limited on choices for a different dial out short code, so thought I'd try the MADN features introduced in 10.1, especially because they are familiar with it. The customer's dialtone is SIP. Will it be as simple as creating a phantom user set up to dial out an ARS that pushes out the main # of the department, or do I do need to do away with the hunt group and rely solely on the phantom user for the group inbound call routing?
After cutting over a customer to their 10.1 Server Edition from a Nortel CS1K, we found out one department was using what sounded like an MADN button(s) to receive what we'd treat as a collective hunt group call, and also to call out occasionally using the department DID as the caller ID. As of now when users call out they will send their own DID, and I have main # of their office coming into a collective call waiting hunt group that has a group mailbox covering calls. I'm kind of limited on choices for a different dial out short code, so thought I'd try the MADN features introduced in 10.1, especially because they are familiar with it. The customer's dialtone is SIP. Will it be as simple as creating a phantom user set up to dial out an ARS that pushes out the main # of the department, or do I do need to do away with the hunt group and rely solely on the phantom user for the group inbound call routing?