Users getting 2mb emtpy VM's to their Email

[craigreilly]

Several users have reported getting 2mb Empty Voicemails to their Exchange Email inbox.
The caller id shows 4000 Receptionist - but she claims she is not sending them calls.

v11
Patton t1 gateway

12:51pm update: It seems when the Receptionist transfers a call to someone, her extension in MyPhone shows "On Internal Call"... then after 2 minutes - it times out and leaves a long a** message.

Any ideas?

Maybe this will be helpful - this is logs for this extension 4926 when right before he received the 2mb empty email.

11:15:48.108|CallLeg.cpp(327)|Log2||CallLeg:nFailure:[CM503003]: Call(494): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:10.0.3.42:5062<br>
11:16:12.170|CallCtrl.cpp(348)|Log2||CallCtrl:nIncomingCall:[CM503001]: Call(495): Incoming call from Ext.4000 to <sip:[email protected]><br>
11:16:12.171|Extension.cpp(1421)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.4000: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.23.10 00:15:65:26:cc:59] PBX contact: [sip:[email protected]:5060]<br>
11:16:12.172|CallCtrl.cpp(540)|Log3||CallCtrl:nSelectRouteReq:[CM503010]: Making route(s) to <sip:[email protected]><br>
11:16:12.172|CallCtrl.cpp(730)|Log2||CallCtrl:nSelectRouteReq:[CM503004]: Call(495): Route 1: Ext:Ext.4926@[Dev:sip:[email protected]:5062]<br>
11:16:12.212|Target.cpp(446)|Log2||Target::makeOneInvite:[CM503025]: Call(495): Calling Ext:Ext.4926@[Dev:sip:[email protected]:5062]<br>
11:16:12.397|Call.cpp(42)|Log3||??:Currently active calls - 6: [368,479,492,493,494,495]<br>
11:16:13.065|CallLeg.cpp(316)|Log3||CallLeg:nAnswer:[CM503002]: Call(495): Alerting sip:[email protected]:5062<br>
11:16:13.065|Extension.cpp(1421)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.4926: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T38G 38.0.23.16] PBX contact: [sip:[email protected]:5060]<br>
11:16:14.084|Target.cpp(446)|Log2||Target::makeOneInvite:[CM503025]: Call(494): Calling @[Dev:sip:[email protected]:5062]<br>
11:16:14.295|CallLeg.cpp(327)|Log2||CallLeg:nFailure:[CM503003]: Call(495): Call to sip:[email protected] has failed; Cause: 486 Busy Here; from IP:10.0.3.14:5062<br>
11:16:14.296|CallCtrl.cpp(862)|Log2||CallCtrl:nRerouteReq:[CM503005]: Call(495): Forwarding: Ext:Ext.9999@[Dev:sip:[email protected]:40600;rinstance=d09971187b22dca6]<br>
11:16:14.302|Target.cpp(446)|Log2||Target::makeOneInvite:[CM503025]: Call(495): Calling Ext:Ext.9999@[Dev:sip:[email protected]:40600;rinstance=d09971187b22dca6]<br>
11:16:14.305|CallLeg.cpp(316)|Log3||CallLeg:nAnswer:[CM503002]: Call(494): Alerting sip:[email protected]:5062<br>
11:16:14.305|Extension.cpp(1421)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.4926: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T38G 38.0.23.16] PBX contact: [sip:[email protected]:5060]<br>
11:16:14.505|CallLeg.cpp(316)|Log3||CallLeg:nAnswer:[CM503002]: Call(495): Alerting sip:[email protected]:40600;rinstance=d09971187b22dca6<br>
11:16:14.505|Extension.cpp(1421)|Log3||Extension:rintEndpointInfo:[CM505001]: Ext.9999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]<br>
11:16:14.509|CallCtrl.cpp(907)|Log2||CallCtrl:nLegConnected:[CM503007]: Call(495): Device joined: sip:[email protected]:5062<br>
11:16:14.510|CallCtrl.cpp(907)|Log2||CallCtrl:nLegConnected:[CM503007]: Call(495): Device joined: sip:[email protected]:40600;rinstance=d09971187b22dca6<br>
11:16:17.370|CallCtrl.cpp(907)|Log2||CallCtrl:nLegConnected:[CM503007]: Call(494): Device joined: sip:[email protected]:5062<br>
11:16:24.580|Call.cpp(1470)|Log2||Call::Terminate:[CM503008]: Call(492): Call is terminated<br>

 

[leejor]

What I suspect, is that the person being transferred to the extension, upon reaching voicemail, hangs up, and the gateway is not set up to disconnect the trunk in a timely manner. That's just a quick guess.

 

[craigreilly]

It seems it was a problem with how the Receptionist phone (a Yealink T28) was setup for Transfers. All the other phones are T38's. The Receptionist is different because it supports 'XML Browser' for a Night Mode script (I can turn the BLF's red or flash or whatever).
I still do not understand the function of the 3 options:
Semi-Attend Transfer
Blind Transfer OnHook
Attended Trans OnHook

Receptionist had on, on, on
What seems to work is off,off,on

So when she transfered a call - when the other end picked up her phone still showed "In Transfer" and after like 2 minutes her phone would beep once. And that is when the user she sent transfer to would get the 2mb voicemail.

 

[ntelecom]

I ran into some problems with a Receptionist using a Yealink phone and transferring to a Yealink phone.

First it was showing a missed call by the receptionist.
So i changed the Semi-Automated Transfer to True.
That fixes the Missed call, but then caused several other errors.
1st, the system would not automatically go to the VM after 20 seconds like programmed.
2nd i would get 2 minute long VM Messages From the Receptionist if that call was ignored.

I had to take off the Semi-Automated Transfer
I also ended up switching to a Grandstream phone for my receiptionist.

 

[craigreilly]

That is where I am at with the settings. We had no issues with this yesterday so I think we are good to go.