Greetings fellow telecom gurus! I was hoping someone could help me with an issue I'm having.
I've recently created a new ACD for our "Help Desk"/Trouble center. Being that the number for the Help Desk has been the same for years I wanted to keep it the same, so I've made that station an x port and call-forwarded it to the new VDN. Everything works here. The problem is that if our one person who works the Help Desk is on the phone or on break I want it to roll to a cover answer group. So I created another station (an x port) to be used as the voice mail/transfer number. In my first vector I make a transfer if the Help Desk is busy, but I transfer to a new VDN. In the second vector I give an announcement letting folks know they are being transfered and then I used a goto line and my x-port station (the one for voice mail). This should automatically go to it's cover path, but it rings once and then goes busy.
Here's what we discovered. There were too many transfers in the switch. Just like you can't chain call forwarding you can't chain VDNs and stations. The fix was to call forward the original Help Desk number to 9,NNX-XXXX(off net and then back in to the VDN the xxxx is the vdn which HAS to be a DID). That is a resolution, but it bites, we're burning one of our precious DIDs.
Does anyone have an alternative to this? Any input would be greatly appreciated.
Thanks,
LittleJohn
I've recently created a new ACD for our "Help Desk"/Trouble center. Being that the number for the Help Desk has been the same for years I wanted to keep it the same, so I've made that station an x port and call-forwarded it to the new VDN. Everything works here. The problem is that if our one person who works the Help Desk is on the phone or on break I want it to roll to a cover answer group. So I created another station (an x port) to be used as the voice mail/transfer number. In my first vector I make a transfer if the Help Desk is busy, but I transfer to a new VDN. In the second vector I give an announcement letting folks know they are being transfered and then I used a goto line and my x-port station (the one for voice mail). This should automatically go to it's cover path, but it rings once and then goes busy.
Here's what we discovered. There were too many transfers in the switch. Just like you can't chain call forwarding you can't chain VDNs and stations. The fix was to call forward the original Help Desk number to 9,NNX-XXXX(off net and then back in to the VDN the xxxx is the vdn which HAS to be a DID). That is a resolution, but it bites, we're burning one of our precious DIDs.
Does anyone have an alternative to this? Any input would be greatly appreciated.
Thanks,
LittleJohn