Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: mgodinez on October 25, 2010, 01:26:03 PM

Title: Failed call tranfer - call ends up at originating device
Post by: mgodinez on October 25, 2010, 01:26:03 PM

Hello,

We have a Mitel 3300 ICP MCD 4.0 controller.  AVST CallXpress 7.91 voicemail platform.

DID A received an outside call.  DID A attempted to transfer the call to DID B.  DID B did not pick, the call ended up ringing back DID A.

SMDR shows FT101 DID B in the trunk/transfer call action field. 

Call rerouting is the same for both DIDs (call re 1st alt. - voicemail).

I can't really see why this happened.  I tested it this morning from my cell phone, and the call transfer completed successfully. 

Any ideas?

Thank you for taking a look see.

Regards,

Mike G.
Seattle, WA

Title: Re: Failed call tranfer - call ends up at originating device
Post by: v2win on October 25, 2010, 01:36:33 PM

Is the no answer recall timer shorter than your call forward no answer timer

Title: Re: Failed call tranfer - call ends up at originating device
Post by: ralph on October 25, 2010, 04:07:18 PM

I agree with v2win on this.   Check the COS no answer recall timer for the transferring phone, the trunks and the called station.  (only because I can't remember which one is controlling its.)

Ralph
www.university-music-on-hold.com (http://www.university-music-on-hold.com)

Title: Re: Failed call tranfer - call ends up at originating device
Post by: mgodinez on October 26, 2010, 02:10:22 PM

Hello,

Thank you for the replies.

The problem was how the user forwarded his DNI line to his cell phone.  Which was the piece of the puzzle that I was missing initially.

We programmed a sys. speed call assn. number that pointed to his cell phone.

He used the feature access code, call forwarding - follow me, plus the sys. speed call number to forward out his calls.  COS was configured to allow transfers out.

Using this code immediately rang back the originating transfer extension.

Using the feature access code, call forwarding - no answer (ext. & int. source), transferred calls successfully.  From an outside line to DID A -> DID A transfers call to DID B -> DID B rings 4 times and then forwards call to cell phone.

Just out of curiosity, why wouldn't the 'call forwarding - follow me' fea. acc. code work for this application.  Does it take the timers out of the equation all together?

Thanks again.

Regards,

Mike G.
Seattle, WA

Title: Re: Failed call tranfer - call ends up at originating device
Post by: v2win on October 26, 2010, 02:24:14 PM

Is the speed call set to override toll controls?

Title: Re: Failed call tranfer - call ends up at originating device
Post by: mgodinez on October 26, 2010, 05:47:19 PM

Quote from: v2win on October 26, 2010, 02:24:14 PM

Is the speed call set to override toll controls?

Hello v2win,

Thank you for your reply.

It is not set to override toll controls.  I'll have to look into toll controls more, to see exactly what it does.  Thank you for pointing this out.

Thanks again.

Regards,

Mike G.
Seattle, WA

Title: Re: Failed call tranfer - call ends up at originating device
Post by: v2win on October 27, 2010, 09:36:52 AM

Set it to yes.

I believe what is happening is the trunk the call is coming in do not have the correct COR or COS to dial out.

The override toll controls will bypass that restriction.