Post OPS MAN telephone directory managment

[mitelmania]

Hi all,

On a cluster with several 3300s at release 4.0 and managed by OPS MAN, the OPS MAN has a "non-mitel node" configured that basically lets us create DN'S against it using OPS MAN and these entries are synched out to the 3300s to create remote DN entries so that all the calls to the DN can be routed through the clustered 3300s to this non-mitel node (Microsoft OCS).

Does anyone have any idea if this type of routing is possible once we migrate to CDD. Do not want to have to have separate ARS tables across the whole of the 3300 cluster with the OCS specifc DNs as this would be unmanagable as more users are added to OCS.


Any insight into how we could achieve this would be very much appreciated.

 

[DoubleUT]

The Remote Directory table does not allow numbers to be added once you go from OPS to GDM. This should be done through ARS.

 

[LoopyLou]

I would think there would not be a problem. What are these DN's that your are creating to route to the OCS? and how are the calls be redirected? With some limitations anything done through OPS can be handled in CDD.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[mitelmania]

What we have in the Network element assigment on the 3300s is a node type "other" with a PBX number assigned to it (this is OCS). This is present on all the 3300s. There is ARS routing with the CEID digits to tell each 3300 how to route this DN back to its home element and on the home element ARS to the OCS server which is connected to the 3300 via SIP. When we deploy an OCS client extension, say DN 2000, to make every 3300 aware of that DN and how to get to we simply create an OPS MAN entry with home elemet of OCS, the ops man sync then puts the entry in the remote dir of each 3300. Its nice and quick to swap a mitel to OCS DN or vice versa.

Thanks for the response !