Acano solution. Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide. September B

Transcription

1 Acano solution Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide September B

2 Contents Contents 1 Introduction How to Use this Guide Commands H323 Gateway Configuration Overview Prerequisites H.323 Gateway Configuration Call Bridge Outbound Dial Plan Rule Configuration Configuring IP Dialing Call Testing Inbound Call from an H.323 Endpoint registered to an H.323 Gatekeeper Inbound Call from an Unregistered H.323 Endpoint by Dialing an IP address Inbound Call from an Unregistered H.323 Endpoint by Dialing <cospace_uri>@ip address Outbound Call to a registered H.323 Endpoint Outbound Call to an Unregistered H323 Endpoint by Dialing an IP address (Call routed with H.323 Gatekeeper) Outbound Call to an Unregistered H323 Endpoint by Dialing an IP address (Call routed without H.323 Gatekeeper) Calling non Acano users from H.323 endpoint Troubleshooting Tips Appendix A SIP Call Control Configuration Appendix B Assigning a certificate/private key pair to the H.323 Gateway Appendix C H.323 Gateway address handling for older gatekeepers Appendix D H.323 Gateway MMP commands Acano solution: H.323 Gateway Deployment Guide B Page 2

3 1 Introduction From R1.7, the Acano server includes a new H.323 Gateway. This gateway is designed to be used only with the Acano Call Bridge, as shown below. Once the call reaches the Call Bridge it is processed according to the normal dial plan rules. Outgoing calls from the Call Bridge devices can also be made to H.323 devices. If the call is into a cospace then it stops at the Call Bridge. Figure 1: Example single combined Acano server deployment with H.323 Gateway This guide covers one of the recommended deployments (a single combined server with the Acano H.323 Gateway enabled on the same Acano server as the Call Bridge) as shown above. The Acano server can be an Acano X3, X2 or X1 server, or be hosted on virtual machines (VM); the term Acano server in this document covers both. In a split deployment we recommend deploying the H.323 Gateway as a Core component, to ensure there is no firewall between the H.323 Gateway and the Call Bridge. Typically, the H.323 Gateway will be deployed on the same Acano server as the Call Bridge. However, the H.323 Gateway may be deployed on a separate core server to the Call Bridge, which is useful for test purposes. In a scalable & resilient deployment you could enable one H.323 Gateway per Call Bridge, again either on the same or separate Acano servers. The commands to configure and enable an Acano H.323 Gateway are the same in all deployments. From R1.8, the IP address for the H.323 Gateway to connect, differs if the Call Bridge and H.323 Gateway are on the same host, compared to them being on different hosts, see section 2.2, step 6. Note: From R1.8, a certificate is required on each H.323 Gateway. The certificate can be signed by an internal CA. Follow the steps in Appendix B to assign a certificate/private key pair to the H.323 Gateway. 1.1 How to Use this Guide This guide follows on from the appropriate Deployment Guide (see the Figure 2). It assumes that you have already completed the instructions within the deployment guide. Only use this guide if Acano solution: H.323 Gateway Deployment Guide B Page 3

4 you want the Acano solution to accept calls from H.323 endpoints and be able to call out to them. This H.323 Gateway deployment guide is intended to be read and acted upon in the order provided. A full list of H.323 commands is provided in the MMP Command Reference guide. In addition to this deployment guide, the reference material shown in the figure below can be found at the Acano Documentation & software page. If you need any technical assistance with the configuration, or you want to report a suspected bug, support@acano.com. Figure 2: Overview of guides covering the Acano Solution Commands In this document, commands are shown in black and must be entered as given replacing any parameters in <> brackets with your appropriate values. Examples are shown in blue and must be adapted to your deployment. Acano solution: H.323 Gateway Deployment Guide B Page 4

5 2 H323 Gateway Configuration 2.1 Overview The H.323 Gateway is a Core component and the recommended deployment is to deploy it on the same server as the Call Bridge. However, the H.323 Gateway can be enabled on a separate Core server. The H.323 Gateway listens on a minimum of two ports: For H.323 incoming calls to be interworked to SIP for forwarding to the Call Bridge For SIP incoming calls from the Call Bridge to be interworked to H.323 before being forwarded We recommend that the H.323 Gateway listens on the same interface as the Call Bridge (but on different port numbers) and is used to listen for both SIP and H.323 calls, see Figure 3. Figure 3: Incoming and outgoing H.323 calls with H.323 Gateway For external outgoing calls from the gateway, we recommend that the H.323 calls are forwarded to a H.323 Gatekeeper (see Figure 4) that deals with routing e.g. using dial plan rules. Note: the H.323 Gateway supports a single next hop. Use the H.323 Gatekeeper s neighboring feature to allow the H.323 Gateway to reach multiple gatekeepers. Acano solution: H.323 Gateway Deployment Guide B Page 5

6 Figure 4: H.323 Gateway with H.323 Gatekeeper In order to accept calls from H.323 endpoints and make calls to them, the Call Bridge must be configured to use the H.323 Gateway as the destination for outgoing calls via the Outbound dial plan, and the H.323 Gateway must be configured to forward SIP calls to a Call Bridge. This section provides example configurations for the recommended deployment that must be adapted to your topology. Note: Release 1.8 introduces improvements in the way that the H.323 Gateway handles outgoing and incoming dial plans for legacy gatekeepers and endpoints. Some old H.323 gatekeepers do not provide the domain in destination addresses for outgoing calls, and cannot handle a domain for incoming calls. These gatekeepers supply and require an E.164 address or H.323 id for the address. Release 1.8 provides new commands to support these devices, see Appendix C for more details Prerequisites The instructions in this section assume that the other components of the Acano solution have been set up and are running. The following ports are required by the H.323 Gateway (see Figure 5). Table 1 Ports required by H.323 Gateway Function Destination Port Type Direction Used on Link(s) Configurable? SIP : Call Bridge 6061 TCP Incoming 6 Yes Media : Call Bridge UDP Incoming 1, 4 No H TCP Incoming 2 No H TCP Incoming 2 No Acano solution: H.323 Gateway Deployment Guide B Page 6

7 The H.323 Gateway provides no firewall traversal functionality. The H.323 call control device that any of your H.323 endpoints are registered to, must provide firewall traversal functionality, and be configured to forward calls to the H.323 Gateway. See the appendix for an example using the Cisco VCS. Unregistered H.323 endpoints must use IP dialing to reach the H.323 Gateway. See section H.323 Gateway Configuration Figure 5: Configuration for H.323 Gateway with H.323 Gatekeeper Follow these steps to configure and enable the H.323 Gateway component on the appropriate Acano server. If your deployment does not use an H.323 Gatekeeper, omit step SSH into the MMP and log in. 2. Configure the interfaces that the H.323 Gateway listens on for incoming H.323 calls (call flow number 2 in Figure 5). The command h323_gateway h323_interfaces <interface whitelist> allows you to configure the interfaces that the H.323 gateway listens for H.323 traffic on (chosen from A, B, C or D). By default the H.323 Gateway listens on no interfaces. For example, configure the h323_interfaces to listen on interface A, enter: h323_gateway h323_interfaces a 3. Configure the interfaces that the gateway listens on for incoming SIP calls from the Call Bridge (call flow number 6 in Figure 5). The command h323_gateway sip_interfaces <interface whitelist> allows you to configure the listening interfaces (for this is interface A). By default the sip_interfaces listens on no interfaces. Acano solution: H.323 Gateway Deployment Guide B Page 7

8 For example, configure the sip interface to listen on interface A h323_gateway sip_interfaces a 4. Configure the ports for the SIP interface to listen on (call flow number 6 in Figure 5). By default the H.323 Gateway uses h323_gateway sip_port 6061 Note: if you wish to change the default port from 6061, and if the H.323 Gateway and Call Bridge are on the same server, make sure you avoid port 5061 which is used by the Call Bridge. 5. Configure the H.323 Gatekeeper s (call control s) hostname or IP address (call flow number 3 in Figure 5). The H.323 Gateway will connect to this IP address for all outgoing H.323 calls and let the call control device handle the routing. For example, if the gatekeeper in the figure above is at IP address h323_gateway h323_nexthop Note: omit this step, if your deployment does not use an H.323 Gatekeeper. 6. Configure the Call Bridge IP address (call flow number 5 in Figure 5). 7. The H.323 Gateway will connect to this IP address for all outgoing SIP calls and let the Call Bridge handle the routing via its dial plan. From R1.8, if the Call Bridge and the H.323 Gateway are on the same host then you must use IP address If Call Bridge and H.323 Gateway on the same host, use: h323_gateway sip_proxy If the Call Bridge and H.323 Gateway are on the different hosts then set the IP address to be the address of the Call Bridge, which must be reachable from the H.323 Gateway. Example of Call Bridge and H.323 Gateway on the different hosts, the IP address of the Call Bridge being h323_gateway sip_proxy Enable the H.323 Gateway component. h323_gateway enable Use the command h323_gateway to check the configuration. A typical output is shown in Figure 6. Acano solution: H.323 Gateway Deployment Guide B Page 8

9 Figure 6 Output from h323_gateway command 2.3 Call Bridge Outbound Dial Plan Rule Configuration Follow these steps to divert all outbound calls through the H.323 Gateway. You need to create an Outbound dial plan rule for the Call Bridge. 1. Sign in to the Acano server s Web Admin Interface. 2. Complete the following fields: Domain: Match all domains i.e. leave empty (see below). SIP Proxy to Use: The SIP interface of the H.323 Gateway Note: if the H.323 Gateway and Call Bridge are on the same host then use IP address :6061. If they are on different hosts, then use one of the external interfaces that the Call Bridge is listening on. Note: The Acano Outbound dial plan rule defaults to using port 5061, if not specified. You need to change this to match the port used by the SIP interface of the H.323 Gateway, which defaults to Encryption: Encrypted Figure 7 Web Admin Interface showing Outbound dial plan with match all domains To divert calls with a specific destination domain through the H.323 Gateway, create an Outbound dial plan rule for the Call Bridge as follows: 1. Sign in to the Acano server s Web Admin Interface. 2. Select Configuration>Outbound calls 3. Complete the following fields (see below): Acano solution: H.323 Gateway Deployment Guide B Page 9

10 Domain: The destination domain. In the example below, the domain All calls to will be diverted through the H.323 Gateway. SIP Proxy to Use: Specify the SIP interface of the H.323 Gateway. If the H.323 Gateway and Call Bridge are on the same host then use IP address :6061. If they are on different hosts, then use one of the external interfaces that the Call Bridge is listening on. Note: The Acano Outbound dial plan rule defaults to using port 5061, if not specified. You need to change this to match the port used by the SIP interface of the H.323 Gateway, which defaults to Encryption: Encrypted Figure 8 Web Admin Interface showing Outbound dial plan with match Note: the H.323 Gateway cannot modify the dialed address. If you require dialed addresses to be modified, then you will need to use an H.323 Gatekeeper in your deployment that is capable of modifying dialed addresses. 2.4 Configuring IP Dialing IP dialing is required when there is no H.323 Gatekeeper i.e. H.323 endpoints are not registered to a call control solution, and calls are made by IP address. For IP dialing to work for calls from both internal and external H.323 endpoints, use the H.323 Gateway as a Core component as above but add a second listening interface for the external calls e.g. on interface B. For IP dialing, we assume that incoming calls are in one of the following formats: IP address which needs to be mapped onto a URI by the H.323 Gateway. Therefore configure the default URI for incoming H.323 calls without a destination. This call can be diverted to a cospace, an Acano user or an Acano IVR. For example, in the MMP, set the default URI to an IVR: h323_gateway default_uri h323ivr@example.com user@ipaddress which is processed by the Call Bridge Incoming dial plan rules; can be a cospace, Acano user or even external user. Note that the Incoming dial plan rules match to the URI not to a callid. Acano solution: H.323 Gateway Deployment Guide B Page 10

11 which is processed by the Call Bridge Incoming dial plan rules; can be a cospace, Acano user or even external user. Note: set call matching for <IP address> or the <domain> on the Web Admin Interface. Acano solution: H.323 Gateway Deployment Guide B Page 11

12 3 Call Testing Depending on the type of call(s) or meetings you intend to have, read and follow the example(s) in the appropriate section(s). Inbound call from an H.323 endpoint registered to an H.323 Gatekeeper, for example a Cisco VCS. Inbound call from an unregistered H.323 endpoint by dialing IP address Inbound call from an unregistered H.323 endpoint by dialing <cospace_uri>@ip Outbound call to a registered H.323 endpoint Outbound call to an unregistered H.323 endpoint (Call routed by H.323 Gatekeeper) Outbound call to an unregistered H.323 endpoint (Call routed without H.323 Gatekeeper) Calling non Acano users from H.323 Note: as H.323 signaling is unencrypted, you can use pcap to obtain an H.323 trace. In addition, the MMP command h323_gateway trace_level <level> provides additional logging to aid troubleshooting by Acano support. You may be asked to provide traces for levels 0, 1 or 2. Note: Release 1.8 introduces improvements in the way that the H.323 Gateway handles outgoing and incoming dial plans for legacy gatekeepers and endpoints. Some old H.323 gatekeepers do not provide the domain in destination addresses for outgoing calls, and cannot handle a domain for incoming calls. These gatekeepers supply and require an E.164 address or H.323 id for the address. Release 1.8 provides new commands to support these devices, see Appendix C for more details. 3.1 Inbound Call from an H.323 Endpoint registered to an H.323 Gatekeeper Example setup: Calling party s H.323 endpoint alias: h323@h323.com Dialing cospace URI: example.cospace@example.com Acano solution: H.323 Gateway Deployment Guide B Page 12

13 Figure 9 Call Flow for Inbound Call from Registered H.323 Endpoint Where: (1) is an H.323 call to example.cospace@example.com (2) is an H.323 call to example.cospace@example.com (3) is a SIP call to example.cospace@example.com Note: From the Call Bridge s point of view, this is an incoming SIP call from the H.323 Gateway. After the call has connected, check the call status in the Web Admin Interface (see Figure 10). Figure 10 Web Admin Interface Showing Active Call Acano solution: H.323 Gateway Deployment Guide B Page 13

14 The call status on the H.323 Gatekeeper, which in this example is a Cisco VCS, shows it as a H.323 call (see Figure 11). The Acano H.323 Gateway performs the interworking. Figure 11 Cisco VCS Showing Call Status Acano solution: H.323 Gateway Deployment Guide B Page 14

15 3.2 Inbound Call from an Unregistered H.323 Endpoint by Dialing an IP address Prerequisite: Set up an IVR Set up cospace with call ID Note: By changing the default URI to an Acano IVR URI, after the incoming call is connected, users can enter a cospace s Call ID to join a specific cospace. For IP dialing to work for calls from both internal and external H.323 endpoints, use the H.323 Gateway as a Core component but add a second listening interface for the external calls e.g. on interface B. h323_gateway h323_interfaces a b Note: the H.323 Gateway cannot traverse NAT or firewalls. The second listening interface for external calls must be internet facing with a public IP address. Example setup: Calling party s unregistered H.323 endpoint name: Brian.ex60 Dialing: where is the called party s H.323 Gateway listening interface Figure 12 Call Flow for Inbound Call from Unregistered H.323 Endpoint Where: (1) is an H.323 call to (2) is a SIP call to h323ivr@example.com Acano solution: H.323 Gateway Deployment Guide B Page 15

16 (3) is a DTMF entry of ID After the call has connected, check the call status in the Web Admin Interface (see Figure 13). Figure 13 Web Admin Interface showing Active Call 3.3 Inbound Call from an Unregistered H.323 Endpoint by Dialing <cospace_uri>@ip address Prerequisite: Create a call matching rule to match the domain Figure 14 Creating a Call Matching Rule For IP dialing to work for calls from both internal and external H.323 endpoints, use the H.323 Gateway as a Core component but add a second listening interface for the external calls e.g. on interface B h323_gateway h323_interfaces a b Note: the H.323 Gateway cannot traverse NAT or firewalls. The second listening interface for external calls must be internet facing with a public IP address. Example setup: Calling party s unregistered H.323 endpoint name: example.mxp Dialing: example.cospace@ where is the called party s H.323 Gateway listening interface. Acano solution: H.323 Gateway Deployment Guide B Page 16

17 After the call has connected, check the call status in the Web Admin Interface (see Figure 15). Figure 15 Web Admin Interface showing Active Call 3.4 Outbound Call to a registered H.323 Endpoint Prerequisite: Create a dial plan rule Example setup: Calling party s Acano user URI: acanouser1@example.com Dialing: h323@h323.com where h323@h323.com is the called party s H.323 endpoint. Acano solution: H.323 Gateway Deployment Guide B Page 17

18 Figure 16 Call Flow for Outbound Call to a Registered H.323 Endpoint Where: (1) is an Acano call to h323@h323.com (2) is a SIP call (3) is an H323 call (4) is an H323 call After the call has connected check the status in the Web Admin Interface (see Figure 17). Figure 17 Web Admin Interface Showing Active Call The call status on the H.323 Gatekeeper, in this example it s a Cisco VCS, shows it as an H.323 call (see Figure 18). The Acano H.323 Gateway performs the interworking. Figure 18 Cisco VCS showing Call Status Acano solution: H.323 Gateway Deployment Guide B Page 18

19 3.5 Outbound Call to an Unregistered H323 Endpoint by Dialing an IP address (Call routed with H.323 Gatekeeper) Note: in this scenario, the H.323 endpoint is unregistered, but an H.323 Gatekeeper routes the call. Prerequisite: Decide on which dial plan rule to use, default rule or a custom rule On the H.323 Gatekeeper (in this example this is a Cisco VCS), in the Dial Plan Configuration set the Calls to Unknown IP Addresses to Direct (see Figure 19) and ensure that the H.323 Gatekeeper can reach the endpoint that you are dialing. Figure 19 Cisco VCS Dial Plan Configuration page For IP dialing to work for calls from both internal and external H.323 endpoints, use the H.323 Gateway as a Core component but add a second listening interface for the external calls e.g. on interface B h323_gateway h323_interfaces a b Example setup: Calling party s Acano user URI: acanouser1@example.com Dialing: where is the called party s H.323 endpoint IP address Acano solution: H.323 Gateway Deployment Guide B Page 19

20 Figure 20 Call Flow for outbound call to an unregistered H.323 Endpoint by dialing an IP address Where: (1) Acano call to (2) SIP call (3) H323 call (4) H323 call When the call has connected, check the status in the Web Admin Interface (see Figure 21) Figure 21 Web Admin Interface showing Active Call On the Cisco VCS, the call will look similar to Figure 22. Acano solution: H.323 Gateway Deployment Guide B Page 20

21 Figure 22 Cisco VCS showing Call Status Acano solution: H.323 Gateway Deployment Guide B Page 21

22 3.6 Outbound Call to an Unregistered H323 Endpoint by Dialing an IP address (Call routed without H.323 Gatekeeper) Note: in this scenario, the H.323 endpoint is unregistered, and there is no H.323 Gatekeeper to route the calls. Prerequisite: The h323_gateway h323_nexthop configuration must be removed if previously set. For example: a. SSH into the MMP and log in. b. Remove the h323_gateway h323_nexthop configuration h323_gateway del h323_nexthop For IP dialing to work for calls from both internal and external H.323 endpoints, use the H.323 Gateway as a Core component but add a second listening interface for the external calls e.g. on interface B h323_gateway h323_interfaces a b Note: the H.323 Gateway cannot traverse NAT or firewalls. The second listening interface for external calls must be internet facing with a public IP address. Example setup: Calling party s Acano user URI: acanouser1@example.com Dialing: where is the IP address of the called party s H.323 endpoint. Figure 23 Call Flow for Outbound Call to a Unregistered H.323 Endpoint Where: (1) is an Acano call to example@example.com Acano solution: H.323 Gateway Deployment Guide B Page 22

23 (2) is a SIP call (3) is an H323 call When the call has connected, check the status in the Web Admin Interface (see Figure 24). Figure 24 Web Admin Interface Showing Active Call 3.7 Calling non Acano users from H.323 endpoint It is possible to configure the Call Bridge dial plan to be able to call Lync or SIP users. These calls are transcoded by the Call Bridge. In this example both the H.323 Gateway and the Call Bridge act as a gateway. It is assumed that the Call Bridge dial plan already allows forwarding of SIP calls to Lync. The H.323 call is interworked into a SIP call to the Call Bridge which then forwards the call to Lync. In this case the Call Bridge handles all transcoding of media. Example setup: Calling party s registered H323 endpoint alias: h323@h323.com Dialing: lyncuser1.lync@acano.demo where lyncuser1.lync@acano.demo is the Lync address for the called Acano solution: H.323 Gateway Deployment Guide B Page 23

24 Figure 25 Call Flow from H.323 endpoint to non Acano user Where: (1) is an H323 call (2) is an H323 call (3) is a SIP call (4) is a Lync call When the call has connected check the status in the Web Admin Interface (see Figure 26). Figure 26 Web Admin Interface Showing Active Call Acano solution: H.323 Gateway Deployment Guide B Page 24

25 On the H.323 Gatekeeper, in this example it s a Cisco VCS, the call will look similar to Figure 27. Figure 27 Cisco VCS Showing Call Status Acano solution: H.323 Gateway Deployment Guide B Page 25

26 4 Troubleshooting Tips After changing the configuration of the H.323 Gateway, the gateway may not work as expected. Reboot the Acano server to solve the issue. The Acano Outbound dial plan rule defaults to using port 5061, if not specified. You need to change this to match the port used by the SIP interface of the H.323 Gateway, which defaults to There is a bug in the Cisco VCS software. Sometimes the settings in Zone > Custom aren't saved. You may need to delete the zone and start again - remember to update the dial plan search rules to match. The MMP command h323_gateway trace_level <level> provides additional logging to aid troubleshooting by Acano support. You may be asked to provide traces for levels 0, 1 or 2. Acano solution: H.323 Gateway Deployment Guide B Page 26

27 Appendix A SIP Call Control Configuration In this appendix the Cisco VCS is used as the example H.323 Gatekeeper/call control device. A VCS Zone must be created and configured: 1. In VCS go to the Zones page (see the two figures below). 2. Enable H323 and then disable SIP (if both are enabled the VCS will use SIP). 3. In Location, set the Peer Address to the IP address of interface that Acano H.323 Gateway is listening on. 4. In Advanced: Change the Zone Profile to Custom. Turn off Monitor Peer Status. Turn on Automatically Respond to H.323 Searches. Acano solution: H.323 Gateway Deployment Guide B Page 27

28 Acano solution: H.323 Gateway Deployment Guide B Page 28

29 Assigning a certificate/private key pair to the H.323 Gateway Appendix B Assigning a certificate/private key pair to the H.323 Gateway From R1.8, a certificate is required on each H.323 Gateway. The certificate can be signed by an internal CA. Follow these steps: 1. Generate a private key and the Certificate Signing Request (.csr) file for the Acano H.323 Gateway application. For information on how to generate a private key and.csr file, refer to one of the Certificate Guidelines on Note: the public key is created and held within the.csr file. 2. Submit the.csr file to the CA (public CA or internal CA) for signing You can use the pki command on the Acano server to generate the private key and.csr file, and submit the pair to an internal CA such as an Active Directory server with the Active Directory Certificate Services Role installed. 3. SSH into the MMP 4. Upload the signed certificate and intermediate CA bundle (if any) to the Acano server using SFTP. 5. Check that the certificate (and certificate bundle) and the private key match pki verify <certicate> <cert bundle/ca cert> [<CA cert>] 6. Assign the certificate (and certificate bundle) and private key pair to the H.323 Gateway h323_gateway certs <keyfile> <certificatefile> [<cert-bundle>] 7. Restart the H.323 Gateway h323_gateway restart Note: if you perform TLS certificate verification by using the command: tls SIP verify enable then certificate verification will be undertaken against the TLS SIP trust store on the Call Bridge and the SIP service on the H.323 Gateway. Use the tls SIP trust <crt bundle> command to set up the TLS SIP trust store. Acano solution: H.323 Gateway Deployment Guide B Page 29

30 H.323 Gateway address handling for older gatekeepers Appendix C H.323 Gateway address handling for older gatekeepers Release 1.8 introduces improvements in the way that the H.323 Gateway handles outgoing and incoming dial plans for legacy gatekeepers and endpoints. Some old H.323 gatekeepers do not provide the domain in the destination addresses for outgoing calls, and cannot handle a domain for incoming calls. These gatekeepers supply and require an E.164 address or H.323 id for the address. Release 1.8 provides new commands to support these devices, see Appendix D for the syntax of all MMP commands for the H.323 Gateway. Figure 28 illustrates how the destination address for calls from legacy gatekeepers can be accepted by appending a domain to the destination address using MMP command h323_gateway sip_domain <sip_domain_uri>. The source address can also have a domain added which can aid dial-back of that user. Using command h323_gateway h323_domain <h323_domain_uri>, appends a domain which enables the Call Bridge to identify where the call originates, and hence support call back. H.323 Endpoint Legacy H.323 Gatekeeper Acano H.323 Gateway Call Bridge H225 setup Destination address: cospace Source address: h323 INVITE To: cospace@sip_domain From: h323@h323_domain Incoming call From endpoint "h323" Figure 28 Adding the domain to the source address Figure 29 illustrates how call back can be made to work for calls originating from legacy H.323 gatekeepers. Using command h323_gateway h323_domain_strip yes removes the domain from the destination if it matches h323_domain and using command h323_gateway sip_domain_strip yes removes the domain from the source address if it matches sip_domain, when making a call to the legacy gatekeeper. Figure 29 Removing the domain for call back Note: dialing an IP address does not require removal of the domain, as the Call Bridge recognizes that it is an IP address and does not append the domain. Acano solution: H.323 Gateway Deployment Guide B Page 30

31 Appendix D H.323 Gateway MMP commands This appendix lists the MMP commands to configure the Acano H.323 Gateway, they are also provided in the MMP Command Reference Guide. Command/Examples Description/Notes Available in release h323_gateway enable/disable/restart The gateway will not start unless it is configured properly. R1.7 h323_gateway certs <keyfile> <certificate file> [<cert-bundle>] h323_gateway certs none h323_gateway h323_nexthop <host/ip> h323_gateway del h323_nexthop h323_gateway default_uri <uri> h323_gateway del default_uri h323_gateway sip_domain <sip_domain > h323_gateway del sip_domain h323_gateway sip_domain_strip <yes/no> h323_gateway h323_domain <h323_domain> h323_gateway del h323_domain h323_gateway h323_domain_strip <yes/no> Defines the name of the private key file and.crt file for the H.323 Gateway application and, optionally, a CA certificate bundle as provided by your CA. (See Appendix B.) Removes certificate configuration Connect to this IP address for all outgoing H.323 calls and let the device at this IP address handle the routing. If this address is not set, only IP dialing works. Typically this IP address is a Cisco VCS/Polycom DMA, and an H.323 trunk is established between the Acano H.323 Gateway and the third party device (H.323 Gatekeeper). The H.323 Gateway does not register with the device, just forwards calls to them the device will need to be configured appropriately to accept these calls. Optional. If an incoming H.323 call has no destination (normally only the case when the H.323 Gateway has been dialed by an IP address) the SIP call is made to whatever default_uri is set. The default_uri may point to an IVR, or directly into a cospace. If it is not set, the call is rejected. Optional. If an incoming H.323 call is made to the gateway without a domain in the destination will be appended to the destination address before the SIP call to the Call Bridge is made. If set to "yes" and "h323_gateway sip_domain" is set, when a SIP call is made to the gateway will be stripped from the source address (if present) before making the H.323 call. Optional. If an H.323 call is made to the gateway without including a domain in the source will be appended to the source address before the SIP call is made. If set to "yes" and "h323_gateway h323_domain" is set, when a SIP call is made to the gateway the <h323_domain> will be stripped from the destination address (if present) before making the H.323 call. R1.8 R1.7 R1.7 R1.8 R1.8 R1.8 R1.8 Acano solution: H.323 Gateway Deployment Guide B Page 31

32 h323_gateway h323_interfaces <interface list> h323_gateway sip_interfaces <interface list> h323_gateway sip_port <port> h323_gateway sip_proxy <uri> h323_gateway restrict_codecs <yes/no> Must be configured in order for the gateway to start, but the actual setting is currently ignored. Ports for the SIP side to listen on. The default is Note: if you wish to change the default port from 6061, and if the H.323 Gateway and Call Bridge are on the same server, make sure you avoid port 5061 which is used by the Call Bridge. Changes do not take place until the gateway is restarted. The H.323 Gateway always expects TLS connections; therefore, "Encrypted" should be selected on outbound dial plan rules on the Call Bridge Set this to the IP address of the Call Bridge, or for multiple Call Bridges use the domain name (through DNS). All incoming H.323 calls will be directed to this uri If set to yes, the H.323 Gateway is limited to a safe set of codecs that are less likely to cause interoperability problems. Currently this set is G.711/G.722/G.728/H.261/H.263/ H.263+/H.264. Codecs disabled by this feature are G and AAC. R1.7 R1.7 R1.7 R1.7 R1.7 h323_gateway disable_content <yes/no> If set to yes, H.239 content is disabled. R1.7 h323_gateway trace_level <level> Provides additional logging to aid troubleshooting by Acano support. You may be asked to provide traces for levels 0, 1, 2 or 3. R1.7 Acano solution: H.323 Gateway Deployment Guide B Page 32

33 2015 Acano (UK) Ltd. All rights reserved. This document is provided for information purposes only and its contents are subject to change without notice. This document may not be reproduced or transmitted in any form or by any means, for any purpose other than the recipient s personal use, without our prior written permission. Acano is a trademark of Acano (UK) Ltd. Other names may be trademarks of their respective owners. Acano solution: H.323 Gateway Deployment Guide B Page 33