3 Primary Rate Interface Configuration
The Acme Packet 1100 and the Acme Packet 3900 support the ISDN Primary Rate Interface (PRI) for higher call-volume customers who want to connect PRI lines (t1,e1), analog trunk lines, analog phones (Extensions), Fax machines, and other analog communications devices to IP PBX/IP telephony systems. The PRI cards provide greater call-volume capacity than the Basic Rate Interface (BRI) card by providing more channels. In the U. S., the PRI card supports 23 b-channels for voice and user data at 64 Kbit per second and 1 d-channel for signaling. In Europe, the PRI card supports 30 b-channels for voice and user data at 64 Kbit per second and 1 d-channel for signaling.
- With the single-port PRI, tdm-profile supports creating only one profile that applies to all spans.
- With the four-port PRI, tdm-profile supports applying a TDM profile to each span for more targeted routing. The tdm-profile sub-element supports enabling a particular span as the timing source, enabling echo cancellation for improved audio quality, and specifying a group of profiles for routing. When configuring multiple tdm-profiles, you can create a profile for each span individually or assign multiple spans to one profile. You can assign the profiles to a route group with either the same number or a different number per profile. For example you can configure a call to go to tdm:profileName, tdm:span:1 or tdm:group:2. You can send the call to a specific tdm interface or a group of them.
Span Configuration
TDM supports creating up to four profiles on the four-port PRI card. You can configure each span exclusively or set several spans (up to four) to share the same configuration. Each span represents a physical network interface. The span-number parameter in tdm-profile indicates the interface to which the profile applies. For example, span-number = 1,2,3,4 means that the profile applies to all spans. span-number = 1 means that the profile applies only to span 1. You can specify more than one span and fewer than four spans in the same profile, for example, span-number = 1,2. During configuration, the system validates that a particular span is assigned to only one profile.
On the single-port PRI card, you can set only one profile and it includes all spans.
Signaling Configuration
Depending on your deployment, you might need the Oracle® Enterprise Session Border Controller (ESBC) to act as the customer premises equipment (CPE) side of the connection or to act as the network (NET) side of the connection.
- The ESBC can act as the NET side of the deployment and connect to a PBX.
- The ESBC can act as the CPE side of the deployment and connect to a network provider's ISDN line.
The system supports the coexistence of multiple profiles for both CPE and NET, and you can configure up to four profiles each. For PRI use pri_cpe and pri_net. For BRI use bri_cpe and bri_net.
Routing Configuration
For control over routing TDM traffic, each TDM profile includes the route-group number parameter that you can use to group profiles together for routing. You can route traffic by setting the following parameters for next-hop in the local-policy configuration:
next-hop = tdm:span:<number> Use span number to specify routing endpoints.
next-hop = tdm:group:<number> Each TDM profile includes route-group number, so that you can group profiles together. The route-group number can address several profiles for routing. During routing, the embedded Asterisk software that the ESBC uses to connect PSTN and VoIP phone services to each other picks the first available span and the first available channel when routing to a group.
next-hop= tdm:<profileName> During configuration, the system checks to confirm that no other profile contains the same routing.