Avaya FAXFINDER SM61 - Manual (Page 15)

RAB; Reviewed:
SPOC 7/12/2011 Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
15 of 34
FaxFinder_SM61
Step Description
12. Administer SIP Trunk Group
For the compliance test, trunk group 12 with the associated signaling group was used for
routing fax calls to/from Session Manager. Trunk group 12 was configured using the
parameters highlighted below. All other fields were set as described in [3].
On Page 1:

The Group Type field was set to sip.
 A descriptive name was entered for the Group Name.
 An available trunk access code (TAC) that was consistent with the existing dial plan
was entered in the TAC field.
 The Service Type field was set to tie.
 The Signaling Group was set to the signaling group shown in the previous step.
 The Number of Members field contained the number of trunks in the SIP trunk
group. It determines how many simultaneous SIP calls can be supported by the
configuration. Each SIP call between two SIP endpoints (whether internal or
external) requires two SIP trunks for the duration of the call.
 The default values were used for all other fields.
change trunk-group 12 Page 1 of 21
TRUNK GROUP
Group Number: 12 Group Type: sip CDR Reports: y
Group Name: PN2 to demoSM COR: 1 TN: 1 TAC: *012
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Member Assignment Method: auto
Signaling Group: 12
Number of Members: 50