I hope i'm posting this in the corret forum and that someone can assist. We have no current support contract and can't get through to Dialogic without one until Monday morning. We have no Voicemail functionality after a planned migration from Exchange Server 2007 to Exchange Server 2013. Everything else works apart from the Dialogic and UM piece. We have a SEVA incident open with Microsoft Premier support who traced the issue to the Dialogic. I've entered the details below - if anyone can assist what i think is a simple misconfiguration i would appreciate it! NO changes were made to the gateway. We tried to dial the user desk phone number and it keeps on ringing without failing back to voice-mail (Exchange 2013 UM). We captured the Wireshark (network) trace on the Exchange UM to see the SIP traffic between Dialogic system & Exchange UM to process the voice-mail. We got a SIP Invite from 10.0.0.180 (Dialogic) to 10.0.0.187 (Exchange 2013) on port 5060 Exchange responded with 100 Trying to Dialogic, And send 302 Moved Temporarily to contact Host Name: NLPRDEX01 (Exchange 2013) on port 5062 Dialogic acknowledged and sends the 2 nd INVITE to same port 5060 again, instead of 5062 to process the voice-mail Again we responded with 100 Trying & 302 Moved temporarily to reach the host port 5062, which ends the phone call to keep on ringing and we didn’t get an option to leave voice-mail. We need the Dialogic to send the INVITE packet to DST port 5062 after we responded with 302 Moved Temporarily. I can provide the Wireshark screen grabs - hope someone can assist thx.
↧