trunk

Syntax

trunk trunk-name {direct-inward-dialing [direct-inward-dialing-number];trunk-type {fxo {tdm-interface interface-name;}fxs {tdm-interface interface-name;}sip sip-trunk-name {peer-proxy-server {address (fqdn fqdn | ipv4–addr ipv4–address);auth-id authentication-id;auth-password authentication-password;codec (G711–A | G711–MU | G729AB)description description;dtmf-method (inband | rfc-2833 | sip-info);port port-number;registrar-address (fqdn fqdn | ipv4-addr ipv4-addr);sip-registration (disable | enable); transport (tcp | tls | udp);}}t1cas-group { signaling { fxo-loop-start;fxo-ground-start;fxs-loop-start;fxs-ground-start;em-wink-start;}time-slots time-slots; }pri-group {time-slots number-range;}tdm-interface tdm-interface-name;}}}

Hierarchy Level

[edit services convergence-services]

Release Information

Statement introduced in Release 10.0 of Junos OS.

Description

Configure a telephony service provider trunk to be used to route calls:

Supported trunk types are FXO, FXS, SIP, and T1. The trunk type determines the parameters you configure. For example, for FXS and FXO trunks, you need to specify only the trunk name and its TDM interface.

You configure trunks, then add them to trunk groups, which you assign to the route patterns of a dial plan. You can use the same trunks for the SRX Series SCS and the SRX Series MGW, so it is best to give them names that are descriptive of their interfaces. For example, you might call the trunk by its interface number. You might call an FXO trunk for interface fxo-1/0/3 fxo-1/0/3.

If one trunk is busy, the next one in the trunk group is tried, and so through the configured trunks.

Options

trunk-name—Name used to refer to the telephony server provider trunk.

Usage Guidelines

For configuration instructions and examples, see the Junos OS Integrated Convergence Services Configuration and Administration Guide.

Required Privilege Level

services—To view this statement in the configuration.

services–control—To add this statement to the configuration.