3.2.7 |
B Channel Allocation |
| Implementing features, see also Manager E B Channel Allocation |
Definition |
| This feature allows you to allocate outgoing connection B channels on an S2M link to different trunk groups. |
| For outgoing calls, only B channels that also correspond to the trunk group are selected (by the code-selected trunk group, overflow trunk group, or LCR-selected trunk group). If there is no free B channel available for this trunk group, the system rejects the connection request and reacts in the way it has been configured. |
| Incoming calls are always accepted if a B channel in the corresponding S2M line is available, regardless of the trunk group. This is usually the B channel offered by the partner. If the remote system or the public network does not support B channel allocation, there is no guarantee that the call will be correctly assigned to the right trunk group. |
| HiPath 3000/5000 Manager E allocates an S2M link to the trunk groups; a route can be assigned to each line (B channel). |
Model-Specific Data |
| |
Dependencies/Restrictions |
| |
| HiPath 3000/5000 V9, Feature Description, Issue 7 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590F100017618 | 2012-06-25 |