Core Issue
The Subscriber Feature Proxy (SFP) does not automatically load default configurations when started for the first time.
Resolution
Perform these steps when the SFP is installed for the first time:
- Log in to the SFP Command Line Interface (CLI) and issue the commit command.
Note: If you see commit N/A, as in this example, proceed to step 2.
/dssfp-SFP>commit
commit N/A
/dssfp-SFP>
If there is a version number next to commit, as in this example, it means there is default data. In this case, proceed to step 3.
dssfp-SFP>commit
commit 5
/dssfp-SFP>
2. To load the default configuration issue the /dssfp-SFP>load -f <filename command.
Note: The filename is located in your install_dir/cfg.
3. If you have default data but still cannot process traffic, check that the listener is configured properly:
1. Under the SFP CLI context transport-mgmt, issue the listen command:
/dssfp-SFP>context transport-mgmt
/dssfp-SFP[transport-mgmt]>listen
2. If the listener is not set under the transport-mgmt context, issue the listen "-i" <ip> ["-p" <port>] ["-t" <transport>] ["-d" <direction>] command.
Note: When the listen command is issued without parameters, the current configuration is displayed. This is a sample output for this command:
[transport-mgmt]>listen -i 192.168.3.4 -p 7890 -t UDP -d internal
Configuration successful.
listen -i 192.168.3.4 -p 7890 -t UDP -d i
For additional information, refer to the Configuring the Server to Receive SIP Messages and Connection Management Configuration sections of the Subscriber Feature Proxy 3.1 Admin Guide.
Problem Type
Voice applications (CRS, PA, CCM Plugins, CER, CCC, MeetingPlace, etc.)
Common Software and Product Issues
Problems after installing software or rebuilding/reinstalling server
Failure Type
Nothing happens
Voice Applications
Call Session Control Platform (CSCP)
Call Session Control Platform Products
Subscriber Feature Proxy (SFP)
