Advertisement
Step
7.
Add a SIP trunk group by using the add trunk-group n command, where n is the
number of an unused trunk group. For the compliance test, trunk group number 1 was
chosen.
On Page 1, set the fields to the following values:
Set the Group Type field to sip.
Choose a descriptive Group Name.
Specify an available trunk access code (TAC) that is consistent with the
existing dial plan.
Set the Service Type field to tie.
Specify the signaling group associated with this trunk group in the Signaling
Group field as previously specified in Step 6.
Specify the Number of Members supported by this SIP trunk group. As
mentioned earlier, each SIP call between two SIP endpoints (whether internal
or external) requires two SIP trunks for the duration of the call. Thus, a call
from a SIP telephone to another SIP telephone will use two SIP trunks. A call
between a non-SIP telephone and a SIP telephone will only use one trunk. In
this solution, each analog endpoint at the branch counts as a SIP telephone.
The default values may be retained for the other fields.
add trunk-group 1
Group Number: 1
Group Name: To SES 50.1.1.50
Direction: two-way
Dial Access? n
Queue Length: 0
Service Type: tie
8.
On Page 3:
Verify the Numbering Format field is set to public. This field specifies the
format of the calling party number sent to the far-end.
The default values may be retained for the other fields.
add trunk-group 1
TRUNK FEATURES
ACA Assignment? n
CTM; Reviewed:
SPOC 11/29/2007
TRUNK GROUP
Group Type: sip
Outgoing Display? n
Numbering Format: public
Solution & Interoperability Test Lab Application Notes
©2006 Avaya Inc. All Rights Reserved.
Description
COR: 1
TN: 1
Auth Code? n
Signaling Group: 1
Number of Members: 24
Measured: none
Prepend '+' to Calling Number? n
Replace Unavailable Numbers? n
Page
1 of
21
CDR Reports: y
TAC: 101
Night Service:
Page
3 of
21
Maintenance Tests? y
AudioCodesMP118.doc
9 of 51
Advertisement
