third party call forward in cluster environement

[brewski6666]

two mitel 3300 Mivb 7.0 in cluster.
the receptioniste (registered in system A) is unable to program third party call forward for an extension on system B.
is it a limitation on the Mivb software or a misconfiguration somewhere in the cluster?

 

[sarond]

There should be no problem using third party call forwarding across the cluster.

What is your "Send Travelling Class Marks" option set to in System Options?
It should be yes.

 

[kwbMitel]

Do you have a feature code assigned against the cluster elements in the cluster form?

@Sarond: Travelling Class Marks have nothing to do with forwarding. Travelling Class Marks maintain COR of the dialing party when the call traverses between controllers (instead of using the COR of the IP Trunk)

**********************************************
What's most important is that you realise ... There is no spoon.

 

[sarond]

I thought they also maintained COS across the network.

 

[AlphaMann]

It is partly a configuration issue.
You need either dial the system ID (as configured in ARS) first and then the feature access code.
Also the COS of the trunks on both sides must allow the feature.
Finally the COR must also be allowed.
You can program a system speedcall to make things simpler.

As for the COS, by default it is a shared form in a cluster. As long as that is not changed a redundant device will maintain the COS to the other controller when it fails over.

 

[brewski6666]

Thank you for your answers.
@KWB:yes, feature codes are assigned against the cluster elements.
@AlphaMann:all COS involved allow the feature.COR is allowed also.
did a test with the system ID as follows:
5552 *555 2356 3817
where:
5552 is the system ID
*555 is the feature code for call forward third party
2356 is the extension to be forwarded
3817 is the extension to forward to.
when i dialed all these digits i got silence for few seconds, the a busy tone and I sow in the IP phone display ''INVALID'
any aidea?

 

[AlphaMann]

Check the logs on the remote end.

 

[sarond]

To reiterate kwb, in your Cluster Elements form do you have a Feature DN set and is it the same length as you extensions (e.g. 4 digits)

With ARS and clustering setup correctly I don't believe you need to enter the CESID, you should just be able to dial *555 2356 3817 (in your example)

Does it work if you try it from a phone on controller B?
Can the receptionist forward an extension on it's own local controller?

It sounds like with the silence you may have a number conflict or have unknown set for ARS digits dialed entry.

 

[brewski6666]

@Sarond: I confirm, teh feature DN is set and is the same lenght as the extensions (4 digits).
yes, the call forward third party works for an extension on the same controller
yes, the receptionist can forward ans extension on it's own local controller.
do you think that I don't need to dial the CESID even if in my exemple (*555 2356 3817) 2356 reside in another controller than the local?

 

[kwbMitel]

Does the COS of the IP Trunk allow the IP trunk to set 3rd party call forwarding?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[brewski6666]

Yes kwb, the IP trunk COS do allow 3rd party call forward.

 

[kwbMitel]

It sounds like everything is setup correctly.

I can confirm that all you should need to do is dial the feature code followed by extension followed by the destination regardless of the location of the extension in the cluster.

You "May" need to press # to indicate that all dialing is completed on a FAC such as this for remote extensions.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[jpruder]

I would try and see if it could be done using ip trunking, then troubleshoot back.