Norstar Call Routing ... 1

[Mostlypc]

With a Norstar Compact ICS 4 x 16 (latest software, 6.1, I think) and CallPilot 100 (although I think we're just using the Norstar Voice Mail portion of it, if that sounds right), and with analog residential trunks in a hunt group ... the way the system is programmed now: let's say Trunk # 1 is busy, so when a caller calls the number associated with Trunk # 1, the hunt group of course rolls over to Trunk # 2; but IF the second line goes unanswered, the caller has to go to a menu to select a mailbox. Question: is there ANY information that is passed along that suggests whom the caller could have been initially trying to contact? such that that info could be used to tell the Norstar switch that that caller REALLY called to speak to someone who answers the Trunk # 1 number most of the time, and so therefore send the call to that person's particular voicemail, without (as we're doing now) having to send the caller to the automated attendant to CHOOSE the particular voice mailbox in order to leave a message? Would that solution be DNIS? If so, is that normally sent by the CO (BellSouth) on normal anaolg (not T-1 or DID) trunks? And if so, can the Norstar switch "read" it. Or is there another solution? Please help. And thanks!

 

[bkrike]

There is not any other additional info.
It sounds like you want calls to go direct to VM box's via direct lines.
If you don’t want T-1 / DID, then the only solution is to have two- two line hunt groups. One for each DN, with each DN having a different published number.

 

[bkrike]

However if you are talking about only a few known people calling you (unlikely,) then you could use the VM CLID routing tables.

 

[Mostlypc]

Thanks very much for the help!