MCD 4.0 SP2 to Exchange Voicemail

[caknfd]

When calling the main number (DID 6868 Speed Dialed to Ext.1501) on a no answer 1501 reoutes to exchange 2010 VM where I get an auto attendant type greeting that allows me to dial an ext. I dial 1616 (happens to any just tested with 1616) it transfers I hear ringing and when it goes to forward back to the users 1616 mailbox the call drops. For testing (the receptionist at 1501 kept answering the call) I set 1501 to reroute always to the same place as the no answer reroute (turned it on and off quickly for testing) when reouted always I call in and dial 1616 it reroutes correctly back to 1616 vm on a no answer. When in the normal mode and the receptionist doesnt answer the transfers to 1616 drop when it goes to forward back to vm.
Another weird thing if I call in two calls at the same time and dial the same extension from both phones the 2nd call wont transfer it drops as soon as it starts to transfer. If I do the same 2 calls but dial 2 different extension numbers the transfers complete OK.

Any Thoughts

Thanks
Craig

 

[LoopyLou]

Any restriction on two SIP trunks being connected? The call comes in goes to Exchange via SIP, rings the MCD a few times then MCD grabs another SIP trunk to send it back. When it tries to drop out it needs to connect two SIP trunks and maybe when it does that you get the call dropping. When you have always setup the call goes to Exchange via a SIP trunk then gets redirected to the MCD which then immediately redirects back to the exchange. That's my thoughts.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[caknfd]

Found this in a release 5.0 SP1 PR1 release note.

MN00370794 Reroute fails on incoming trunk call to SIP
REPORTED IN SW LOAD 10.0.2.8
Call Flow
1. Incoming trunk call on no answer reroutes to SIP VM Auto Attendant.
2. Auto Attendant transfers to an extension on the 3300
3. In a No Answer condition the call will not reroute back over SIP using the 1st Alternative

WORKAROUND = Configure the second reroute alternative.

Couldn't assign just the 2nd alt had to leave the 1st alt in there but add a 2nd alt to the users ext to the same place for the workaround to work.

Craig

 

[LoopyLou]

Did it work?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[caknfd]

I did but I couldn't just use the 2nd Alt. When i just used the 2nd Alt Alone the same thing happened. But if I set both the 1st and 2nd Alt's to go the the SIP VM it started working. Customer is one of those with out Software Assurance so i can't upgrade.

Craig

 

[LoopyLou]

Did you go into the first alternative and set it to Last?. If you go that you don't have to define an extension in the first alternative.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.