codian.gif IP GW 3510
host: IPGW
Index
Help contents > Getting Started with the IP gateway > Getting started with the IP gateway

Getting started with the IP gateway

Ensure you have correctly completed the physical setup of the IP gateway following the instructions contained in the Getting Started Guide that accompanied the unit.

Note: Codian recommends that you change the admin account to use a password as soon as possible. To do that, go to Users, click the admin link, and provide the required user information.

Step one: Configure Ethernet Port B settings

The default setting for the IP GW Ethernet ports is auto-sensing mode. If the switch ports to which you connect the IP GW are not also set to auto-sensing mode, then you need to configure the IP GW Ethernet ports to use the same speed and duplex mode. Both ends of the Ethernet connection must be configured in the same way. For example, either configure both ends of the link to be auto-sensing or configure both ends to operate at the same speed and duplex.

During your initial configuration of the IP gateway following the instructions in the Getting Started Guide, you will have configured Port A using the command line interface.

Note: To establish a 1000Mbps connection, both ends of the link must be configured as auto-sensing

  1. To configure Ethernet Port B, go to Network > Port B.
  2. Enter the IP address, subnet mask, default gateway and DNS name server for the port.
  3. Enter a secondary name server and domain name if required.
  4. Click Update IP configuration.

Step two: Configure an H.323 gatekeeper and/or SIP registrar (optional)

If you have H.323 endpoints, using an H.323 gatekeeper can make it easier for callers to make their call. You can configure the IP gateway to use an external gatekeeper or its own built-in gatekeeper.

If you have SIP endpoints, using a SIP registrar can make it easier for callers to make their call.

For more information refer to Configuring gatekeeper settings and Configuring SIP settings.

The built-in gatekeeper can be used to bridge between two networks allowing endpoints connected to each port to use the same gatekeeper. This enables callers on the same port to call each other without the call being routed through the IP gateway, whilst calls from one port to the other are routed transparently through the IP gateway. For more information, refer to Using the built-in gatekeeper to bridge between two networks

Step three: Configure the auto attendant menus

Depending on the configuration of your dial plan, and the settings for failed calls, callers can be connected to the auto attendant. You can configure the auto attendant to allow callers to:

 

To configure auto attendant menus, go to Menus >Menu builder

When you configure endpoints and call groups you can choose whether those endpoints and call groups will appear in an internal address book that can be displayed by the auto attendant.

For more information, refer to Configuring auto attendant menus, Configuring failed call settings, Understanding the dial plan, Configuring call groups, and Configuring endpoints.

Step four: Configure an operator (optional)

An operator is a person who can put calls through on the IP gateway. You can use the dial plan to automatically connect calls to an operator, you can allow callers to directly dial an operator, and you can have an operator as an option on the auto attendant. An operator connects the calls one by one as calls reach the top of the operator's call queue. An operator can put calls through to configured endpoints and call groups that have been given names in the system, or to any other endpoint by manually entering the IP address or E.164 number of the endpoint.

For more information, refer to: Understanding operator features and Configuring operator settings.

Step five: Add endpoints (optional)

You can configure endpoints to work with the IP GW. For configured endpoints, the operator can simply choose the endpoint's name from a list, rather than having to type in the endpoint's address when a caller wants to be connected to that endpoint.
When you configure an endpoint, you can select whether or not that endpoint will appear in the internal address book, thereby enabling a caller to connect to that endpoint, without the caller having to know its address.

For more information, refer to: Configuring endpoints.

Step six: Configure failed call settings

Calls can fail for a number of different reasons. For each failure type, you can configure the IP gateway to act in one of three ways. You configure the failed-call action by port; that is, you can configure different actions for each port.

For more information refer to Configuring failed call settings.

Step seven: Configure the dial plan

The default behavior of the IP gateway is to reject all calls. You must configure a dial plan to allow permitted calls to be placed.
There are a number of different ways in which you can use the dial plan. For example, you can configure a particular prefix that will forward calls to the operator and another to connect callers to the auto attendant.

For more information, refer to the topics: Understanding the dial plan, Adding and updating dial plan rules, Example dial plan rules, Dial plan syntax, and Displaying and testing the dial plan.

Step seven: Train the operator and instruct callers how to make calls through the IP gateway

If you have an operator, you must provide them with some training in how to answer and connect calls; in the case of an operator who has not used a video phone before, it might also be a good idea to provide some guidance for that. For more information, refer to Using the Codian IP gateway — for operators.

End users will need to know how to make calls through the IP gateway. For example, are you going to provide a quick-dial option for contacting the operator? Are you going to allow callers to dial IP addresses? For more information, refer to Dialing the IP gateway — for end-users.