Transferred call not going into the voicemail box of the phone that the call was transferred to

[NewbieCarol]

I know this is probably going to be something easy. We have a CM 6.3 and Unified Messaging 2013. We have 3 6408d+'s set up with bridged buttons to an "X" ported extension. When someone calls the "X" ported extension and they need to transfer the call to someone else and they don't answer, the caller is put back in the voicemail of the "X" ported extensions voicemail. Any thoughts on why this is happening?

 

[janni78]

This usually is an issue with SIP based VMs, the SIP headers contains the first called extension and the VM will look for that.


"Trying is the first step to failure..." - Homer

 

[kyle555]

What if you warm transfer? At least that will show UM that the 2nd leg of the call was unanswered and should get the transfer destination's mailbox to answer.

It's probably something about the order of the history headers or diversion headers that Avaya does first-to-last and MS last-to-first.

 

[NewbieCarol]

But so far this is the only extension this is happening to. Granted it's the only situation where we have bridged calls being transferred. I'm stumped.

 

[NewbieCarol]

So i just tested this again only this time i had the "X" ported station wait until either someone answers or a voicemail answers. And this time the correct VM picked up. So they aren't going to just be able to hit transfer, dial the other party, and the hit transfer again.