Manual

Support for QSIG Over BRI and Q.931 Over BRI Backhaul
Provisioning Tasks
7
Cisco MGC Software Release 9.5(2)
Collecting QSIG/Q.931 Over BRI Backhaul Path Data
The QSIG/Q9.31 over BRI Backhaul component type represents an QSIG/Q.931 over BRI Backhaul
signaling service to a particular Cisco BRI voice gateway. Refer to the “Restrictions” section on page 2
for more information on the Cisco media gateways that can be used for this feature. You must be ready
to enter the following data:
• MML name
• Component description
• MML name of the associated external node
• Q.931 call model side (user or network)
• MDO file name (ETS_300_102, Q931, or ETS_300_172)
• Customer group ID
• Customer group table
• Call reference length (0 through 2 bytes)
Note If you are using the ETS_300_102 or Q931 protocol files, call reference should be set to 1.
If you are using the ETS_300_172 protocol file, call reference should be set to 2.
You can define the parameters for your QSIG/Q.931 over BRI Backhaul signaling services in Table 12
in the “Provisioning Worksheets” section on page 51.
Collecting IP Route Data (optional)
The IP route component type represents a static IP route. IP routes are required for this feature only when
the Cisco MGC hosts are not on the same subnet as the Cisco media gateways. If your system requires
IP routes, you must be ready to enter the following data for each route:
• MML name
• Component description
• Destination host name or IP address
• Subnet mask of destination (optional)
• Next hop router IP address
• Local IP address
• Priority
You can define the parameters for your IP routes in Table 13 in the “Provisioning Worksheets” section
on page 51.
Collecting Backhaul TCP Link Data
The Backhaul TCP link component type represents the connection between the Cisco MGC and a
Cisco BRI voice gateway. You must be ready to enter the following data:
• MML name
• Description of this component
• Signaling type (BRI)