The served party (FXS interface) can be configured through the Web interface (see
Configuring Call Forward on page 270) or ini file to activate one of the call forward modes.
These modes are configurable per endpoint.
Notes:
• When call forward is initiated, the device sends a SIP 302 response with
a contact that contains the phone number from the forward table and its
corresponding IP address from the routing table (or when a proxy is
used, the proxy’s IP address).
• For receiving call forward, the device handles SIP 3xx responses for
redirecting calls with a new contact.
24.5.1 Call Forward Reminder Ring
The device supports the Call Forward Reminder Ring feature for FXS interfaces, whereby
the device's FXS endpoint emits a short ring burst, only in onhook state, when a third-party
Application Server (e.g., softswitch) forwards an incoming call to another destination. This
is important in that it notifies (audibly) the FXS endpoint user that a call forwarding service
is currently being performed.
Figure 24-2: Call Forward Reminder with Application Server
The device generates a Call Forward Reminder ring burst to the FXS endpoint each time it
receives a SIP NOTIFY message with a “reminder ring” xml body. The NOTIFY request is
sent from the Application Server to the device each time the Application Server forwards an
incoming call. The service is cancelled when an UNSUBSCRIBE request is sent from the
device, or when the Subscription time expires.
The reminder-ring tone can be defined by using the parameter CallForwardRingToneID,
which points to a ring tone defined in the Call Progress Tone file.
The following parameters are used to configure this feature:
To Next Page
Loading...
Need help?
General
