1

Oracle Communications
Analog/BRI/Fax Knowledge Transfer Session

PRI and BRI enhancements
Miklos Tirpak
July, 2017
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted
Table Of Contents
 New interfaces supported
 What’s new in the configuration
 Upgrade notes
 Useful commands
12/7/2017 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
New interfaces supported
 BRI (EuroISDN): Digium 1B433LF quad-port card - AP1100
https://www.digium.com/sites/digium/files/bx3x-series-bri-cards-user-manual.pdf
 Analog (US-only): Digium 1A8B04F 8-port card (4 FXO + 4FXS) - AP1100

https://www.digium.com/sites/digium/files/analog-telephony-card-8-port-user-manual.pdf
Existing PRI interfaces are kept supported:

Digium 1TE133F single-port card - AP1100
Digium 1TE435BF quad-port card - AP1100 and AP3900
Functional Specification: BRI, Analog and Fax Support

https://cgbu-doccenter.us.oracle.com/cs/groups/public/documents/document/ynvf/mdi0/~edisp/cgbu_024446.docx
What’s new in the configuration?
 Per-span configuration (PRI/BRI), per-channel configuration (analog)
 Network vs. CPE side individually per span (PRI/BRI)
 Timing source individually (PRI/BRI)
 CRC4-checking (PRI)
 Inbound overlap-dial (PRI/BRI)
 Routing-groups (PRI/BRI/analog)
 New routing options in local-policy (PRI/BRI/analog)
 “activate-config” can identify the config changes (PRI/BRI/analog)
 Additional analog features in a separate presentation, for example fax
transcoding and fxo-tuning
Per-span configuration
tdm-config
state enabled
logging disabled
line-mode bri
tone-zone de
calling-Pres allowed_not_screened Multiple tdm-profiles can be configured
caller-ID no
tdm-profile
name profile1 Span number(s) the profile applies to
signalling bri_cpe
switch-type euroisdn
b-channel 1-2
d-channel 3
span-number 1,2 Route-group the profile belongs to
route-group 0
term-resistance enabled
timing-source 1
BRI (+ some PRI) configuration attributes
tdm-profile CPE vs Network side
name profile1 Rx – Tx pins of the BRI interface are swapped in SW!
signalling bri_cpe
switch-type euroisdn
b-channel 1-2
d-channel 3 Fixed for BRI
span-number 1,2
route-group 25 Enable a termination resistance to close the circuit,
line-build-out 0 likely need at the CPE side (BRI only)
framing-value ccs
coding-value ami Clock source (BRI+PRI)
term-resistance enabled 0: provide clock (usually network side)
1: preferred source
timing-source 2
2: second preferred source
rx-gain 2.2 …
tx-gain 3.0
echo-cancellation enabled Configure inbound overlap dial (BRI+PRI)
overlap-dial yes
incoming-pattern _2222[1-3].|_2233[4-5][567]. Pattern rules for overlap dial (BRI+PRI)
options
New PRI configuration attribute
(to be backported to ECz7.3.0m2+)
tdm-config
state enabled
logging disabled
line-mode e1
tone-zone de
tdm-profile Enable CRC4-checking over the E1 interface (Eurpoe).

name profile1
signalling pri_cpe
switch-type national
b-channel 1-15,15-31
d-channel 16
framing-value ccs
coding-value hdb3
crc4-checking enabled
PRI configuration example
PSTN PRI interface

provider1
PRI interfaces
ESBC PBX
PRI interface
PSTN
provider2
PRI configuration example
tdm-profile
name provider1 Separate profiles for the two providers to be able to fine-
signalling pri_cpe tune the parameters individually, for example gain or echo
span-number 1 canceller.
route-group 10
timing-source 1 CPE side and synchronize to the clock of the provider
tdm-profile
name provider2
signalling pri_cpe
span-number 2 Common route-group, the local-policy can refer to that:
route-group 10 next-hop tdm:group:10
timing-source 2 Or it can route to a specific profile:
tdm-profile next-hop tdm:provider1
name pbx
signalling pri_net
Network side and provide clock to the PBX
span-number 3,4
route-group 20
timing-source 0
Outbound routing
local-policy
policy-attribute
next-hop tdm:<profileName> (PRI/BRI/analog)
This translates to one of the followings
or
next-hop tdm:span:<spanNumber> (PRI/BRI)
next-hop tdm:channel:<channelNumber> (analog)
or
next-hop tdm:group:<groupNumber> (PRI/BRI/analog)
The first available span/channel of the group is selected
Inbound routing
There is no change in the inbound direction
 Calls are received from the “tdmRealm” realm.

 Source of the call can be further identified by the caller number
Overlap dial
 Support for inbound overlap dial is added
 After the incoming ISDN Q.931 SETUP, the ESBC waits for additional digits in
INFORMATION messages until:
 the inter-digit timer expires:
 8 sec if there is no matching pattern, i.e. there has not been enough digits received yet.
 3 sec if there is already a matching pattern, i.e. there are theoretically enough digits received to route the call
out, but the match is still ambiguous.
 or there is a clear match in the incoming-pattern rules that does not allow any more
digits, and no other pattern would match even if more digits were received.
 or a “Sending Complete” is received.
Incoming-pattern rules
 Set the incoming pattern to enhance the user experience with overlap-dial.
 “incoming-pattern” is an ORed combination of multiple rules that can be:
 extension numbers
 or match patterns:
 X matches any digit from 0-9
 Z matches any digit from 1-9
 N matches any digit from 2-9
 [1237-9] matches any digit in the brackets (in this example, 1,2,3,7,8,9)
 . wildcard, matches one or more characters
 ! wildcard, matches zero or more characters immediately
Example: The secretary's number ends with 70 only and the user extensions with 71XX, 72XX, and 73XX:
incoming-pattern 4933120070|_493312007[1-3]XX
Activate-config
“activate-config” identifies the configuration changes and can inform the user about the
following cases:
 Changes can be applied runtime

 Changes result in call interruption
 Restart is required
Upgrade from previous releases
The upgrade is seamless, all the features remain supported.
The configuration gets converted automatically:
tdm-config tdm-config
line-mode e1
tdm-profile tone-zone de
name profile1 calling-Pres allowed_not_screened
line-mode e1 caller-ID pai
signalling pri_cpe
span-number 1 tdm-profile
line-build-out 0 name profile1
tone-zone de signalling pri_cpe
calling-Pres allowed_not_screened span-number 1,2,3
caller-ID pai line-build-out 0
options number-of-spans 3 route-group 0
SIPD – Asterisk communication
Asterisk is running on the ESBC to drive the Digium cards. There is no change here.
ESBC
tdm_p0
SIP SIPD interface SIP 198.51.100.1 Asterisk BRI/PRI/Analog
203.0.113.1 203.0.113.2
Configure steering pools

and media-manager!
Useful commands
Enter the Asterisk CLI from shell: asterisk –vvvvvrc
Asterisk commands: ACLI commands:
pri show spans show tdm spans

pri show span <num> show tdm span <num>
dahdi show status show tdm satus
dahdi show channels show tdm channels
dahdi show channel <num> show tdm channel <num>
pri set debug on span <num>
sip set debug on
Oracle Confidential – Internal/Restricted/Highly Restricted

1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1

Caricato da

Copyright:

Formati disponibili

Oracle Communications

Analog/BRI/Fax Knowledge Transfer Session

 Analog (US-only): Digium 1A8B04F 8-port card (4 FXO + 4FXS) - AP1100

Existing PRI interfaces are kept supported:

Functional Specification: BRI, Analog and Fax Support

tdm-profile Enable CRC4-checking over the E1 interface (Eurpoe).

PSTN PRI interface

The first available span/channel of the group is selected

 Calls are received from the “tdmRealm” realm.

 Changes can be applied runtime

Configure steering pools

Asterisk commands: ACLI commands:

pri show spans show tdm spans

Potrebbero piacerti anche