Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

interconnect number - IP Trunk - Cluster 1

Status
Not open for further replies.

danramirez

Programmer
Oct 25, 2009
1,136
ES
Guys,

MCD6.0

I have the idea of having read somewhere that Interconnect Restriction could be set in a way that the originating device will carry its Interconnect Number across a cluster.

This way one could restrict sets of certain Interconnect Number of using Trunks that belong to another controller across the network.

Imagine Extension in node A to have interconnect number 2, the IP trunking that links controllers A and B will have Interconnect Number 3, and PRI Trunks in node B will have interconnect number 4.

How do I restrict a call originated by an Extension in node A to use trunks in node B?

Note that if I restrict "From 2 to 4" call will go through as MCD will treat this call as IP Trunking (Interconnect num 4) the one using the PRI trunk.

Please let me know if what I think to have read is true or it was a dream.

Regards,

Daniel


 
I thought this as well.
I have not tried but is it "Send Travelling Class Marks" in the System Options form.
 
that's the one "sarond", thank's a lot.

Traveling Class Marks
Description
Traveling Class Marks allow callers in a private network to access features and services based on the their own Class Of Service (COS), Class of Restriction (COR), and Interconnect Number, rather than on those of the incoming trunk on the remote system.

The TCM can be used

for displaying or logging purposes by the remote system.

to restrict or grant features and services.

restrict calls from using a particular route out of the system.

to disallow the caller to call a particular destination.

Conditions and Feature Interactions
TCM is available on systems with 3300 ICP Release 8.0 or higher software. Calls to systems that do not have the required software are processed as usual.

For TCM to operate correctly, all systems within the cluster or network must have identical COR Group, COS and Interconnect Restriction programming. This can be achieved through System Data Synchronization .

All trunk types, including TDM and IP, that support the DPNSS protocol will support TCM.

TCM are sent only if the calling or called party is either a set or an attendant console.

Programming
To enable TCM, set "Send Travelling Class Marks" in the System Options form to "Yes."

Note: Failing to add a suite to the Guest Rooms form will cause calls to and from non-primary suite members to use the member's COR, COS and Interconnect Restrictions instead of those belonging to the primary suite member as intended by the TCM feature.

Operation
None.



 
Correct you don't send interconnect you send COS/COR by using travelling class marks. That will dictate which trunks your call can use on the other controller.

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.
 
Loopy, I have tested it and it seems that Interconnect Number is also sent along COS/COR. I got "Call Barred" when trying to call over trunks on the remote controller.

The description of this feature says:

"Traveling Class Marks allow callers in a private network to access features and services based on the their own Class Of Service (COS), Class of Restriction (COR), and Interconnect Number"

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top