VARI - TL65
Signaling diagram for incoming traffic
Format
VARI = D1D2D3D4D5D6D7D8 |
||
D1D2D3D4 = |
0000 |
Reserved |
D5 = |
0 - 3 |
See Table Table 1. |
D6 = |
0 - 1 |
See Table Table 2. |
D7 = |
0 - 1 |
See Table Table 3. |
D8 = |
0 - 1 |
See Table Table 4. |
0 |
1 |
2 |
3 |
|
Diversion after deflection *1) |
||||
Yes |
X |
. |
X |
. |
No |
. |
X |
. |
X |
Bypass IRD *2) |
||||
Yes |
X |
X |
. |
. |
No |
. |
. |
X |
X |
*1) |
Only valid for incoming call deflect requests from H.323 private trunks. If call deflect request does not contain "replace the dialed number/name with deflected-to number/name" and "diversion after deflection" information, then the value set in the route configuration will be used to control both the features. If call deflect request contains only "replace the dialed number/name with deflected-to number/name" information, then this will used to control both "replace the dialed number/name with deflected-to number/name" and "diversion after deflection", that is, the value set in D5 will be discarded. |
*2) |
Only valid for incoming call deflect requests from H.323 private trunks. If a call deflect request does not contain Bypass IRD information, then the value set in the route configuration will be used to control the "Bypass of IRD" feature. |
0 |
1 |
|
Emergency route |
||
No |
X |
. |
Yes |
. |
X |
0 |
1 |
|
Support of Generic Functional Protocol (GFP) |
||
No |
X |
. |
Yes |
. |
X |
0 |
1 |
|
Overlap receiving |
||
No |
X |
. |
Yes |
. |
X |
Function
The parameter indicates the signal diagram variations for incoming traffic.
Example
- Overlap receiving is not permitted and no support of Generic Functional Protocol (GFP).
VARI = 00000000
Support for Generic Functional Protocol (GFP)
No
Overlap receiving
No