Mediant 1000 Digital
Fast Track Guide 18 Document #: LTRT-63802
7. In the ‘ISDN Termination Side’ field (applicable only to ISDN protocols), select ‘User Side’
when the PSTN or PBX side is configured as ‘Network side’, and vice-versa. If you don’t
know the Mediant 1000 ISDN termination side, choose ‘User Side’ and refer to the ‘Status &
Diagnostics>Channel Status’ screen. If the D-channel alarm is indicated, choose ‘Network
Side’.
8. In the ‘Control Protocol Type’ field, select the control protocol type you use (MGCP or
MEGACO).
9. In the ‘Call Agent IP’ field, enter the Call Agent IP address if your enterprise’s network
doesn’t feature a DNS server that automatically defines the Call Agent’s IP address. If you
have a DNS server, the field is optional.
10. In the ‘Call Agent Port’ field, enter the Call Agent port. The default port is 2427 (MGCP) and
2944 (MEGACO).
11. In the ‘Call Agent Domain Name’ field, enter the Call Agent domain name. When using the
DNS server option, enter the domain name of the Call Agent operating with the Mediant
1000. The DNS server automatically detects the Call Agent’s IP address from the domain
name.
12. For MGCP take the following steps:
• In the ‘Gateway Name’ field, enter a name to the device (for example, ‘gateway1.com’).
Ensure that the name you choose is the one that the Call Agent is configured with to
identify your Mediant 1000.
• In the ‘Naming Method’ field, select the naming method you want to use. You can select
‘Endpoint Naming’ or ‘Trunk Naming’.
♦ If you select Endpoint Naming:
In the ‘Endpoint Name’ field, enter an intuitive endpoint prefix. Ensure that the
endpoint prefix you choose is the one that the Call Agent works with. In the
‘Endpoint Numbering Offset’ field, you can enter a value to offset the numbers that
represent the gateway’s endpoints.
♦ If you select Trunk Naming:
In the ‘Trunk Name’ and ‘Endpoint Prefix’ fields, enter intuitive prefixes. Ensure that
the definitions you choose are the definitions that the Call Agent is configured with
to identify your Mediant 1000. In the ‘Trunk ID Offset’ field, you can enter a value to
offset the numbers that represent the gateway’s trunks.
13. For MEGACO take the following steps:
• In the ‘Physical Name Pattern’ field, enter an intuitive name to identify the gateway’s
physical termination in the format: [name1]*[name2]*. The first asterisk represents the
number of the trunk; the second asterisk represents the number of the endpoint. For
example, ‘tgw/t*/c*’.
• In the ‘Logical RTP Name Pattern’ field, enter an intuitive name to identify the gateway’s
RTP termination in the format: [name]*. The asterisk represents an internal identification
assigned by the gateway to the RTP termination. For example, 'gw/rtp/*'.
• In the ‘Logical ATM Name Pattern’ field, enter an intuitive name to identify the gateway’s
ATM termination (if used) in the format: [name]*. The asterisk represents an internal
identification assigned by the gateway to the ATM termination. For example, 'gw/atm/*'.
14. Click the Reset button and click OK in the prompt; the Mediant 1000 applies the changes
and restarts.
15. After the gateway is reset, if different configuration is required per trunk, refer to Section 3.5
on page 23. Otherwise, set the ‘PCM Law Select’ field (
Advanced Configuration>TDM Bus
Settings
), select ‘A-law’ for E1 trunks and ‘µ-Law’ for T1 trunks.
Note: MGCP/MEGACO users should continue with Section 3.5 on page 23.
To Next Page
Loading...
Need help?
General
