AltiGen comm MAXCS 82 Softswitch Deployment Guide
Have a look at the manual AltiGen comm MAXCS 82 Softswitch Deployment Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 29 AltiGen comm manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
MAXCS 8.0 All-Software Solution Deployment Guide Page 31 of 39 SIP Trunk Profile Field Description SIP Protocol Field Not Sent (default) – Do not send transmitted caller ID FROM Header – Send the caller ID using the SIP FROM header P-Preferred Identity – Send the caller ID using the SIP P-Preferred Identity header P-Asserted Identity – Send the caller ID using the SIP P-Asserted Identity header Carrier can accept any number This is the default. Carrier can only accept Calling Number with minimum x digits Enter the number of digits, and then enter a calling number in the field below the table in case the carrier cannot accept configured numbers. Carrier can only accept assigned numbers as Calling Number If you select this option, specify “assigned numbers” by clicking the Add button and entering the numbers. To edit or delete a number you added, select it and click the Edit or the Del button. Enter a calling number in the field below the table in case the carrier cannot accept configured numbers. Send Caller Name Check to also send the caller name to callees. Enable Standard Record- Route Header Check this box if the SIP service provider uses SIP Record-Route and the SIP trunk cannot make or receive calls. If it already works, DO NOT CHECK or UNCHECK this box. [Service provider Bandwidth.com with Edgewater Route require this checked] Incoming DID Number Field When a call comes in, the SIP trunk uses To Header or Request URI as the DID/DNIS number Enable Fax Trunk Routing This feature is supported on AltiGen SIP trunks only. If the extension is a fax extension and Fax Trunk routing is checked, that means the SIPSP should use the Fax Username and Fax password of SIP Trunk profile instead of regular username and password of SIP Trunk to negotiate with the SIP Trunk. If the extension is a fax extension but Fax Trunk routing is unchecked, that means the SIPSP should use the regular username and password of the SIP Trunk to negotiate with the SIP Trunk side. Fax User Name – The user name for fax routing Fax Password – The password for fax routing Step 13: Configure a Codec Profile Next, configure a Codec Profile for the SIP trunks in Enterprise Manager: 1. In MAXCS Administrator, select VoIP > Enterprise Network Manager. 2. Click the Codec button on the Quick Launch bar (this is different from the IP Codec tab). 3. Check whether a profile named SIPTrunk has been preconfigured for you.
Page 32 of 39 MAXCS 8.0 All-Software Solution Deployment Guide If it has already been configured, confirm that the settings are correct. If this profile was not preconfigured, click Add and create a profile with the following parameters: For the name, enter SIPTrunk. Set the Selected Codec to G.711 Mu-Law (use the Add and Remove buttons as needed) Set DTMF Delivery to RFC 2833 Set SIP Early Media to Enable Set SIP Transport to UDP Click Advanced and set both packet lengths to 20 ms Step 14: Assign the Codec Profile to the Two SIP Servers Next, assign the SIPTrunk Codec Profile to the two SIP trunk servers. 1. In Enterprise Manager, click the Servers button on the Quick Launch bar. 2. Open the IP Codec tab. 3. Determine whether the following servers were preconfigured for you: 65.254.44.194 74.81.71.18 4. If these servers were preconfigured for you, confirm that each server is assigned to the Codec Profile SIPTrunk. If they were not preconfigured for you, click Add, add the first server, and set the Codec Profile to SIPTrunk. Repeat for the second server.
MAXCS 8.0 All-Software Solution Deployment Guide Page 33 of 39 Step 15: Configure NAT To confirm that NAT support has been configured, 1. Click the IP Networks tab and confirm that both of the NAT support checkboxes are selected. If they have not been selected, check both boxes. 2. Close Enterprise Manager.
Page 34 of 39 MAXCS 8.0 All-Software Solution Deployment Guide Step 16: AltiGen SIP Trunk Configuration Note: These steps apply only to deployments that are using AltiGen SIP Trunks. Before you begin, retrieve the configuration details from the MaxCS Private Cloud portal, in the SIP Services section of the General tab of your account. If your deployment uses SIP services from another AltiGen-certified SIP Trunk carrier, you will need to get the specific configuration details from that provider. Configuration details will vary from one provider to another. You will begin by configuring the first server. Configure the First Server 1. Log into the MAXCS Cloud portal and retrieve the details on the General tab of your account. 2. Switch back to MAXCS Administrator. You should be in the SIP Group Configuration page. If not, open it now. 3. Add a SIP Group for the AltiGen SIP trunk. In our example, it is named it AltiGen. Check the option AltiGen Trunk Group. If you also have a Fax Trunk account, check the Enable fax trunk routing option and enter the user name and password. (If you do not have a Fax Trunk account, or if you are not sure, leave this option unchecked. You can configure it later as needed.) Server 1 Server 2
MAXCS 8.0 All-Software Solution Deployment Guide Page 35 of 39 4. Highlight the SIP group that you just created and add the first AltiGen SIP server (Server 1). The domain is atgn1.siptrunk.com. 5. After you add this server, switch to the Register tab on the right and configure the parameters as follows: For Domain, enter atgn1.siptrun.com. For SIP Server IP Address, enter the SIP Trunk IP address of the first SIP trunk server: 65.254.44.194. For User Name, enter the SIP Trunk Username number (from the order in the MaxCS Private Cloud portal). In our example, this username is 5812129034. For Password, enter the SIP Trunk Password (from the order in the Cloud Services portal). Click Hide/Show Password to see it. Set the Register Period to 60. Set SIP Source Port (Non-TLS) to 5060. Set SIP Destination Port to 5060.
Page 36 of 39 MAXCS 8.0 All-Software Solution Deployment Guide Configure the Second Server Next, configure the second server. 1. Highlight the SIP group AltiGen, and add the first AltiGen SIP server (Server 2). The domain is atgn2.siptrunk.com. 2. In the Register tab, configure these parameters for this second server: For Domain, enter atgn2.siptrunk.com. For SIP Server IP Address, enter the SIP Trunk IP address of the second SIP trunk server: 74.81.71.18. For User Name, enter the SIP Trunk Username number (from the order in the MaxCS Private Cloud portal). In our example, this username is 5812129034. For Password, enter the SIP Trunk Password (from the order in the Cloud Services portal). Click Hide/Show Password to see it. Set the SIP Register Period to 60. Set SIP Source Port to 5060. Set SIP Destination Port to 5060.
MAXCS 8.0 All-Software Solution Deployment Guide Page 37 of 39 Enable Channels 1. For Server 1, open the Settings tab and change SIP Protocol Field to From Header. 2. Repeat this step for Server 2, setting SIP Protocol Field to From Header. 3. Open the Channel Assignment window. 4. Highlight multiple SIP trunk channels and then click Assign Group. Assign them to the AltiGen SIP Group. Make sure that those channels remains highlighted, and check one of their check boxes. This should enable all of the selected channels. Check Your Configuration To confirm that your configuration is correct, 1. Look in the SIP Group Configuration window. The status for both servers should show as UP.
Page 38 of 39 MAXCS 8.0 All-Software Solution Deployment Guide 2. In Trunk view, these trunks should show as Idle. Step 17: Configure Inbound Routing Carriers send 11 digits as DNIS; configure your inbound routing rules accordingly. Step 18: Configure Out-Call Routing Configure out-call routing as appropriate for your system. Refer to the MAXCS Administration Manual for details and instructions. Step 19: System Configuration At this point, calls should come into the system. Your next steps are to configure out-call routing and other internal processing rules. Refer to the MAXCS ACM Administration Manual for instructions: Chapter 4, System Configuration Chapter 26, Enterprise Manager Step 20: Configure Polycom Phones If the organization has Polycom phones, refer to the MAXCS 8.0 Polycom Phone Configuration Guide for instructions on how to configure those IP phones. This document is available in the AltiGen Knowledge Base. Note: Configuring Polycom phones in Release 8.0 is very different from the configuration process used in previous releases.
MAXCS 8.0 All-Software Solution Deployment Guide Page 39 of 39 AltiGen Technical Support AltiGen provides technical support to Authorized AltiGen Partners and distributors only. End user customers, please contact your Authorized AltiGen Partner for technical support. Authorized AltiGen Partners and distributors may contact AltiGen technical support by the following methods: You may request technical support on AltiGen’s Partner web site, at https://partner.altigen.com. Open a case on this site; a Technical Support representative will respond within one business day. Call 888-ALTIGEN, option 5, or 408-597-9000, option 5, and follow the prompts. Your call will be answered by one of AltiGen’s Technical Support Representatives or routed to the Technical Support Message Center if no one is available to answer your call. Technical support hours are 5:00 a.m. to 5:00 p.m., PT, Monday through Friday, except holidays. If all representatives are busy, your call will be returned in the order it was received, within four hours under normal circumstances. Outside AltiGen business hours, only urgent calls will be returned on the same day (within one hour). Non-urgent calls will be returned on the next business day. Please be ready to supply the following information: Partner ID AltiGen Certified Engineer ID Product serial number AltiW are or MAXCS version number Number and types of boards in the system Server model The telephone number where you can be reached