...
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Trunk Provisioning - Egress Ip Attributes H323 Call Forwarding |
|---|
|
| |
Image Modified
There are no Call Forwarding parameters for DEFAULT_H323 type of Egress Ip Attributes.
...
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Trunk Provisioning - Egress Ip Attributes SIP Call Forwarding |
|---|
|
| |
Image Modified
The following fields are displayed:
| Caption |
|---|
| 0 | Table |
|---|
| 1 | Egress Ip Attributes Call Forwarding |
|---|
|
| |
Parameter | Description |
|---|
Diversion History Info Interworking | Enable flag to allow interworking between Diversion and History-Info header as per RFC 6044. The supports up to 12 History-Info entries and 10 Diversion entries. When this flag is disabled, only the first and last entries are maintained when History-Info or diversion transparency is disabled. | Note |
|---|
Diversion History Info Interworking is only visible when either Diversion or History-Info header is selected as the egress call forwarding header. Diversion and History-Info Transparency configuration controls are ignored when it is enabled. This parameter has precedence over the others. |
|
Data Mapping | Use this parameter to define how to map the diversion or redirecting data. Options are: none – No Diversion information is egressed.
diversion – Diversion information is sent out as SIP Diversion Header.
pkHeaders – Diversion information is sent out as proprietary PK Headers.
|
Diversion Header Transparency | When enabled, the ingress Diversion header is passed through unchanged. Call forwarding data mapping transparency applies to Diversion header only. |
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.