FXS supplementary services description
408
SmartWare Software Configuration Guide
35 • FXS interface configuration
Conferencing
When executing a conference, all involved calls will be handed to a given call-router conference service. It is
then the responsibility of this service to initiate the conference. Conference services are configured in the Con-
text CS and are protocol specific. The sip-conference service can be used to address a SIP Media Server for con-
ferencing according to RFC4240 (see section,
“SIP conference-service”
on page 520).
Conferencing can only be executed if the second call was originated by the local subscriber. If the second call is
an incoming call and the local subscriber tries to conference, the call toggle service will be executed.
Mode:
Interface FXS
Call park
The call park service allows parking an ongoing call on a specific number. This park number starts with a spe-
cific Park Code that must be configured with the ‘service-pattern’ command. After the user pressed ‘flash’ to
open a new call and the dialed number starts with the defined park service-pattern, the service will be executed
5s after the last digit has been pressed or the user completes the number with the ‘#’ character. This service is
not handled locally, which means another entity must be contacted that offers it.
On some SIP servers, it is possible to park a call on specific number by using the blind-transfer feature. This is
what the FXS park-call service achieves in an FXS/SIP call. It forces the SIP endpoint to execute a blind trans-
fer where the Refer-To header contains the park number.
Mode:
Interface FXS
Step
Command
Purpose
1
[name](if-fxs)[name]#[no] route confer-
ence dest-service
<service-name>
Specifies the routing destination for a conference.
The no form of the command clears an existing
route.
Step
Command
Purpose
1
[name](if-fxs)[name]#[no] park
Enables or disables the call park feature.
