We have an 8 site SCN (mix of IPO SOE, 403's, 406's and 412 ALL @ 3.1 v56 and VM Pro 3.1 v18). Central site has PRI and VM Pro server (WIN2K3). Remotes connected via PtP fiber (all units connected by CAT5 patch to Transition Networks 10/100 fiber tranceivers set to 10/H to a central 3COM 16 port auto-negotiating switch. The VM PRo server is also connected to this as well as feed to the customer network. Narrowing down the problem has been a challenge, but here is our best guess as to the scenario.
BOTTOM LINE: When a call is placed to a Hunt Group and no one answers, the call goes to a VM Pro Group>Leave action (menu w/ choices of who to call via Transfer actions.
IF I select an option to transfer to a member of the hunt group (lets say x1100, member of HG 1990), the call rings-no-answer w/ no visible attempt to cover to VM in Call Status.
If x1100 is on SAC/DND the call goes to VM
If I select an option to transfer to a person NOT in the hunt group(locally or somewhere else in the SCN) , the call goes to VM normally.
COMPLICATING FACTORS:
This does NOT happen with hunt groups @ the central site (not a PRI issue as it happens internally as well).
This is NOT a result of the outside fiber links as I now have a 403 in the central server room connected by fiber tranceivers the same as the remote sites and the same scenarios occur).
Using an Assisted Transfer action results in silence until the call goes to VM via a leave mail action from the No Answer box of the Assisted transfer, usually cutting off some or all of the greeting.
This seems particularly bad since we went to 3.0+.
JT
BOTTOM LINE: When a call is placed to a Hunt Group and no one answers, the call goes to a VM Pro Group>Leave action (menu w/ choices of who to call via Transfer actions.
IF I select an option to transfer to a member of the hunt group (lets say x1100, member of HG 1990), the call rings-no-answer w/ no visible attempt to cover to VM in Call Status.
If x1100 is on SAC/DND the call goes to VM
If I select an option to transfer to a person NOT in the hunt group(locally or somewhere else in the SCN) , the call goes to VM normally.
COMPLICATING FACTORS:
This does NOT happen with hunt groups @ the central site (not a PRI issue as it happens internally as well).
This is NOT a result of the outside fiber links as I now have a 403 in the central server room connected by fiber tranceivers the same as the remote sites and the same scenarios occur).
Using an Assisted Transfer action results in silence until the call goes to VM via a leave mail action from the No Answer box of the Assisted transfer, usually cutting off some or all of the greeting.
This seems particularly bad since we went to 3.0+.
JT