CFFM 3rd Party Via DISA over Tandem 1

[MitelInMyBlood]

Has anyone ever managed to get 3rd party cffm working across a tandem intermachine switch via DISA?

Ie, Dial into the tandem using DISA then invoke your CFFM 3rd party codes. I can't seem to get it to work, tho it works on the local machine. Can't get it to work across the network of interconnected machines. CLA O S on all have the feature allowed.

3300/ SX2K mixed network


Original MUG/NAMU Charter Member

 

[kwbMitel]

I've had mixed results.

My workaround involved having 1 system as the entry point for external DISA and then setting up DISA for each remote system that is dialable via the cluster CEID's.

Involves a lot of dialing but speeddials can be invoked to help.

e.g.
system 1 has DID for DISA

system 2, 3, and 4 etc have an identical code as system 1.

The DISA numbers are not typically named and thus not populated via OPS in the remote Directory.

To access system 3 DISA you first dial the DISA number, then once authenticated, dial the CEID of system 3 and the DN for DISA. (DISA number needs to match extension length for cluster programming)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Thanks. That should work as that theoretically makes you 'local-authenticated' to each system, which appears to be the issue. Our DISA is on an intermachine tandem (2K) that serves as a trunking gateway to our corporate network. This dates back to when all was TDM and the original tandem was an old SG with a 32-link DSU and resale software (MFRD-23). It's a 2K Light today hosting 5 DSU nodes and 2 pers (expanded) for fax lines, modems, etc. (old theories die hard).

We've not given the FAC to the endusers, preferring to be contacted when the rare occasion happens that 3rd party CFFM is required. With this workaround I see even more justification to keep this as a 'technician function'


Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

Interesting however that if I am in the office I can do it to a phone hosted on any node from a phone on my 3300. Hmmmm.....

Original MUG/NAMU Charter Member

 

[kwbMitel]

you could try and use CCS to see what digits are being received at the remote system in the 2 scenarios.

I think you'll just prove that it is not possible with a trunk, or with DISA.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

I can only do it (remote) in the shop from the 3300, not from a phone on any of the 2Ks. On the 2Ks you can only do it locally to another set on the same machine. Weird. CCS would be a nightmare to try and watch as too much traffic. May try it tho.

Original MUG/NAMU Charter Member

 

[kwbMitel]

Does the 2K have the Feature Code defined in the Cluster Element Form?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

I think you have hit on something related.

The 2K gateway is not a member of the cluster, yet traffic has to route across it between members of the cluster. Hence there are ARS entries in it to pass the CEID + 4 to follow to the respective members. However, in checking I see no ARS in the tandem to accommodate the Feature codes. If this fixes it you will get a *

Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

Didn't fix it

However I still feel that the non-clustered tandem sitting in the middle (hub & spoke) is the problem, tho clustering between the elements (4) otherwise works fine.

Original MUG/NAMU Charter Member

 

[kwbMitel]

I'm pretty sure the systems need to be clustered to allow the remote feature activation.

If you can capture the digits on the destination system from a working scenario, you might be able to use ARS to emulate it.

In the meantime, the earlier method of authenticating to each system should work.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

I agree w/your diagnosis. However, on-net it really does not matter as the purpose behind remote/3rd pty cffm would likely be in a business recovery/disaster scenario where we couldn't get to the office anyway. Thanks for the help!!

Original MUG/NAMU Charter Member