Fiberme FCM630A Series Manual
  1. Manuals
  2. Brands
  3. Fiberme Manuals
  4. PBX
  5. FCM630A
  6. Manual

Fiberme FCM630A Series Manual

Hide thumbs Also See for FCM630A Series:
Table of Contents

Advertisement

Quick Links

Download this manual
FIBERME Communications LLC.
FCM630A Series IP PBX - Busy Camp-on Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FCM630A Series and is the answer not in the manual?

Questions and answers

Related Manuals for Fiberme FCM630A Series

Summary of Contents for Fiberme FCM630A Series

  • Page 1 FIBERME Communications LLC. FCM630A Series IP PBX - Busy Camp-on Guide...

  • Page 2: Table Of Contents

    Table of Contents OVERVIEW ........................... 2 CALL COMPLETION FEATURE CODE.................. 3 CALL COMPLETION FOR LOCAL EXTENSIONS ............... 4 Configuration ................................. 4 Sample Application............................... 5 CALL COMPLETION FOR TRUNKS ..................6 Configuration ................................. 6 Using SIP Register Trunks .......................... 6 Using SIP Peer Trunks ..........................8 Sample Application.............................

  • Page 3: Overview

    OVERVIEW Busy Camp-on/Call Completion is a feature where the PBX will camp on a called party and inform the caller as soon as the called party becomes available given the previous attempted call cannot be successfully established. When trying to reach an extension which is already busy, the caller could request the FCM630A to camp on the called party by dialing the call completion request code.

  • Page 4: Call Completion Feature Code

    CALL COMPLETION FEATURE CODE The feature code for call completion request can be modified on web GUI → Call Features → Feature Codes page. The default setting is *11 for “Call Completion Request” and *12 for “Call Completion Cancel”. Figure 1: Call Completion Feature Code P a g e...

  • Page 5: Call Completion For Local Extensions

    CALL COMPLETION FOR LOCAL EXTENSIONS Configuration 1. On FCM630A web GUI → Extensions/Trunk → Extensions page, create or edit an extension (e.g., 2000) to bring up the dialog in below figure. 2. Click on “Features” tab and make sure the following are configured: •...

  • Page 6: Sample Application

    Sample Application Assuming “user A” is using FCM630A extension 2000, and user B is using FCM630A extension 2001. Both extensions have “Enable CC” selected and “CC Mode” set to “Normal” as mentioned above. 1. Extension 2000 calls extension 2001. 2. The call fails to be established due to the following possible reasons: a) Extension 2001 is busy, e.g., talking on the phone.

  • Page 7: Call Completion For Trunks

    CALL COMPLETION FOR TRUNKS Configuration Call completion for trunks is applicable to SIP register trunks and SIP peer trunks. Two FCM630As must be first configured with SIP trunks to each other. For the sake of the following illustration, we name the two FCM630As involved in this example FCM1 with IP address 192.168.6.133 and FCM2 with IP address 192.168.5.143 respectively.

  • Page 8: Figure 4: Create Sip Register Trunk

    Figure 4: Create SIP Register Trunk • Type: Select “Register SIP Trunk”. • Host Name: Enter the IP address of the FCM to register to. • Username: The extension number on the FCM to register to. • AuthID: Same as Username. •...

  • Page 9: Using Sip Peer Trunks

    7. Configure inbound and outbound rules on two FCMs to make sure the extensions on FCM1 can reach the extensions on FCM2 through the SIP register trunk and vice versa. 8. For the extensions on both FCM630A that you would like to use call completion, go to the FCM630A web GUI→...

  • Page 10: Figure 7: Edit Sip Peer Trunk

    Figure 7: Edit SIP Peer Trunk 1.2. Access “Advanced Settings” tab and set following options: • “Enable Heartbeat Detection”: selected. This setting is optional, if activated it will help to check the status of the trunk. • “Enable CC”: selected. Figure 8: SIP Peer Trunk –...

  • Page 11: Sample Application

    2. Similar to step 1, on FCM2, create a SIP peer trunk with FCM1. 3. Check the trunks status on web GUI → System Status → Dashboard. If configured successfully, the status for the trunk should show as “Reachable”. Figure 9: SIP Peer Trunk Status 4.
  • Page 12 b) If extension 5001 rejected the call or the call went to timeout when 1005 called 5001, 5001 is considered as available after a new call is completed. This means extension 5001 has to initiate a new call or answer another incoming call and the new call hangs up.

Table of Contents