talkunity1
IS-IT--Management
Hello everyone. Please forgive me if this has been covered previously. (I did a search before starting this post, but didn't find a similar topic.)
Is there a way on BCM450/400/50 to map/route/assign outbound line access or internal dialing of an ASM port based on the DN of the originating user, either to a specific line pool/bloc or specific LINE port, or to a specific analog station port on an ASM media bay module?
Consider the following scenario: A small company with 3 different departments (Dept. A, B, and C) with multiple employees in each dept having a T7316 phones with 2 Intercom buttons. Consider a system-wide routing arrangement or "speed dial equivalent" like "734" so that employees can just pick up their handset (or press Intercom) and dial 734. The appropriate outbound line is chosen or their call is directed to a specific internal DN that is an ASM port.
Is there a way to configure call routing such that when users in Dept. A dial 734 they get routed to LINEx or POOLx, and users in Dept. B dialing the same 734 get routed to LINEy or POOLy, and Dept. C folks get to LINEz or POOLz? A dial plan would then absorb the 734 and initiate an outbound dial string on the line.
Alternatively, instead of accessing a specifically mapped LINEn/POOLn, a user dialing 734 could ring a specific ASM port DN as the destination.
There needs to be a specific relationship between the individual user DNs in a department and the outbound destination (determined by their department) they reach. The user DNs are not numerically sequential nor do they contain patterns that could be parsed with wildcards in a routing rule. The members of a department are subject to change as people move around.
This is for outbound calling ONLY. There might be a need to block the "734" so that an inbound caller couldn't dial it and end up getting access...
Example:
The theoretical DNs of the users in each department are shown below. Consider that POOLx,y,z are line pools with a single POTS line and conventional dialtone on each. There may be additional departments and user DNs added, but there would always be only one LINE or POOL associated with a department.
Dept. A (3 users, when dialing 734, route invokes a dial plan and goes out POOLx)
DN 123
DN 112
DN 149
Dept. B (2 users, when dialing 734, route invokes a dial plan and goes out POOLy)
DN 109
DN 198
DN 117
Dept. C (3 users, when dialing 734, route invokes a dial plan and goes out POOLz)
DN 171
DN 173
DN 150
Please note that all other calls would be processed by existing routing and dial plans using existing line POOLA, and normal dialing of all other numbers, internal and external, would not be affected.
Thoughts?
Thank you!
Is there a way on BCM450/400/50 to map/route/assign outbound line access or internal dialing of an ASM port based on the DN of the originating user, either to a specific line pool/bloc or specific LINE port, or to a specific analog station port on an ASM media bay module?
Consider the following scenario: A small company with 3 different departments (Dept. A, B, and C) with multiple employees in each dept having a T7316 phones with 2 Intercom buttons. Consider a system-wide routing arrangement or "speed dial equivalent" like "734" so that employees can just pick up their handset (or press Intercom) and dial 734. The appropriate outbound line is chosen or their call is directed to a specific internal DN that is an ASM port.
Is there a way to configure call routing such that when users in Dept. A dial 734 they get routed to LINEx or POOLx, and users in Dept. B dialing the same 734 get routed to LINEy or POOLy, and Dept. C folks get to LINEz or POOLz? A dial plan would then absorb the 734 and initiate an outbound dial string on the line.
Alternatively, instead of accessing a specifically mapped LINEn/POOLn, a user dialing 734 could ring a specific ASM port DN as the destination.
There needs to be a specific relationship between the individual user DNs in a department and the outbound destination (determined by their department) they reach. The user DNs are not numerically sequential nor do they contain patterns that could be parsed with wildcards in a routing rule. The members of a department are subject to change as people move around.
This is for outbound calling ONLY. There might be a need to block the "734" so that an inbound caller couldn't dial it and end up getting access...
Example:
The theoretical DNs of the users in each department are shown below. Consider that POOLx,y,z are line pools with a single POTS line and conventional dialtone on each. There may be additional departments and user DNs added, but there would always be only one LINE or POOL associated with a department.
Dept. A (3 users, when dialing 734, route invokes a dial plan and goes out POOLx)
DN 123
DN 112
DN 149
Dept. B (2 users, when dialing 734, route invokes a dial plan and goes out POOLy)
DN 109
DN 198
DN 117
Dept. C (3 users, when dialing 734, route invokes a dial plan and goes out POOLz)
DN 171
DN 173
DN 150
Please note that all other calls would be processed by existing routing and dial plans using existing line POOLA, and normal dialing of all other numbers, internal and external, would not be affected.
Thoughts?
Thank you!
