- 1. D ATA S H E E T ConferenceManager 10.0Sonexis
ConferenceManager is an in-house audio conferencing bridge that
eliminates the costlypay-as-you-go fees of subscription-based
services, while setting new standards for security andease of use.
Designed to work within existing voice and data networks and
available with a fullyintegrated Web conferencing option
ConferenceManager has been deployed by hundreds ofleading
organizations with minimal cost, effort, or administration. In
fact, Sonexis has deliveredmore audio conferencing bridges than any
other vendor serving the small and medium-sizedenterprise.DISCOVER
THE BENEFITS:An Irresistible Economic Story The financial picture
isclear. Sonexis ConferenceManager provides a rapid,compelling
payback. Your service provider just cantcompete. A minimal one-time
investment and your will be scheduling, launching, and recording
confer-organization begins saving immediately regardless ofences;
collaborating over files in real-time; evenhow your conferencing
usage scales. Watch yourinviting new conference attendees on the
fly.savingsnot your costsskyrocket.ConferenceManager makes it very
easy for everyone.Better still, you pay only for what you need.
With ourFamiliar applications (like Microsoft Outlook, Lotusunique
architecture youre never more than a licenseNotes, and the Web
browser) provide the interfaceskey away from increasing users,
adding Web func-that make ConferenceManager accommodating
fortionality, or changing from one protocol to another.your
end-user; while simple Web-based administra-Simply put, its the
best thing to happen to conferenc- tion provides the flexibility
you need to meet youring.organizations needs.Unprecedented Ease of
Use and Administration TheSensible Protection for Your
Business-Criticalability to adapt ConferenceManager to your
changing Information ConferenceManager is an outstandingneeds
through a simple software upgrade is just the audio conferencing
bridge with integrated Webbeginning of ConferenceManagers unmatched
ease conferencing that sits on your network under yourof use.
Whether youre an end-user or the systemmanagement.
ConferenceManagers smart, embed-administrator, youll be surprised
that conferencingded security features keep your information safe
fromcan be so easy. Simply plug ConferenceManager intooutside
intrusion. You maintain control of criticalyour voice (PSTN) or
data network (VoIP) and within business information and the
security proceduresminutes your organization that protect it.
2. ConferenceManagers powerful features give you fast,
full-functionv ActiveTalker highlights whos speakingaudio
conferencing that is cost-effective, easy to use, and secure. or
whos got the noisy liney Host can easily label sub-conference rooms
and navigate between themuHost can easily identifyparticipants by
name wxVisual indicator shows Web Participants can signal: Host can
divide participantsconference participationinto (up to) ten private
When theyre ready to returnAdministrators can easilyto the main
conference; or sub-conferencesmanage users through When they have a
question in listen-only lecture mode CONFERENCEMANAGER 10.0 Audio
Conferencing Supports 12 to 576 ports PSTN (PRI, CAS) Integrated
Web conferencing (optional) Supports 12 to 600 ports VoIP (SIP,
H.323) Supports 5 to 600 seats Scheduled or ad-hoc
(reservation-less) conferences Scheduled and ad-hoc
(reservation-less) conferences Conference scheduling and management
through Cross platform and no download for participation Microsoft
Outlook, Lotus Notes, or Web interface Scheduling and mgmt via
Outlook, Notes, or Web Integrated, Web-based host control panel
Pre-defined and saved conference rooms Real-time speaker
identification (ActiveTalker) Application- and document-sharing
Emergency Management and Blast Dialout Integrated with audio
console Supports up to ten sub-conferences off the main Interactive
whiteboard, annotation tools, and notepad conference Follow-me Web
browsing Advanced IVR for greetings and help menu Text chat,
Q&A, polling, and voting Dial-in or dial-out Automatic e-mail
invitations, Quick inviteSystem Information Multiple conference
announcement options OPERATING SYSTEM: Windows 2008 Server (tone,
name, none) PROCESSORS: Intel 5504TM Quad Core 2.0GHz Audio
recording MEMORY: 4GB Fully Buffered DDR3 RAM Call detail records
STORAGE: 300GB HD JITC Certified REDUNDANCY: Dual HD (RAID 1) and
power (optional) ADMINISTRATION: Web, attached KVM, or terminal
services NETWORKING: Dual Gigabit Ethernet(10BASE-T, 100BASE-TX,
and 1000BASE-T, RJ45 output)300 Seco RoadMonroeville, Pennsylvania
15146 EXPANSION: 4 PCI expansion slots888-476-6394 or 888-4SONEXIS
MOUNTING SYSTEMS: 2U 19www.sonexis.com v10.0 3. KEY FEATURES- Intel
2600 Chassis - SR2600URLX- Intel 5504 Quad Core 2.0GHz processor-
3GB Fully Buffered DDR3 RAM- Dual Intel Pro/1000 EB Ethernet ports-
2 Riser Slots With Intel Adaptive Slot Technology- Cheetah 300GB
SAS Hard Drive- RAID 1 and redundant power (optional)MOTHERBOARD
Intel S5520UR Server BoardPROCESSOR/CACHEINPUT/OUTPUTCPU Intel 5504
Quad Core 2.0 GHz withUSB 2 USB ports 4MB Intel smart cacheSerial
Ports 1 RJ45 Serial B PortSystem Bus 1066MHz/1333MHz system
busKeyboard Stacked PS/2 keyboard and mouse/Mouse portsSYSTEM
MEMORYSYSTEM BIOSMemory Twelve DIMM socketsBIOS Type Intel
28F320C3B 4MB Flash ROMCapacity 3GB Fully Buffered DDR3 RAM Five
3.5 IDE drive bays (w/o CMA) 27.75 (704.8mm) Dual-channel memory
bus (memory One Optional Hard Drive or Tapemust be populated in
pairs) Drive BayMemory Type DDR3 Fully Buffered DIMMs IDE Slim
Optical Drive BayON-BOARD DEVICES DIMENSIONSChipset Intel E5520
Chipset Height 3.44 (87.30mm)IPMI IPM Interface v.2.0 Width (w/o
Rails) 16.93 (430mm) Support for Intel Remote (w Rails) 17.77
(451.3mm)Management Module 3 and LocalDepth (w/o CMA) 27.75
(704.8mm)Control Panel (w CMA) 33.0 (838.2mm)Network Dual Intel
Gigabit Ethernet Weight 65 lbs (29.5kg)Controllers Supports
10BASE-T, 100BASE-TX, Color Blackand 1000BASE-T, RJ45
outputGraphics ATI with 64MB of video memoryEXPANSION SLOTSPOWER
SUPPLY 2 Riser Slots - Intel Adaptive Slot 750W AC power supply 4
PCI Express buses (2x8 or 4x4)AC Voltage 100 - 220V, 50/60Hz, 12
amp 1 PCI-X bus DC Output 12V + 5V + 3.3V < 840W Draw 2 amps
steady, 6.8 max, per supply Environ. 750 BTUs steady, per
supplySonexis Technology, Inc. | 300 Seco Road | Monroeville, PA
15146 | 1-866-2SONEXIS (1-866-276-6394) [email protected] |
www.sonexis.com 4. SONEXIS PRE-IMPLEMENTATION SITE REQUIREMENTSTDM
Systems (T1 and/or PRI connections):Direct TELCO connection: 1.
Order the necessary T1/CAS or T1/PRI circuits. 2. Obtain a CSU/DSU
(Channel Service Unit/Data Service Unit).Sonexis ConferenceManager
supports the following protocols, tell your provider you need a
circuitconfiguration that matches one of the types below: CAS
-Frame Type: ESF/B8ZS or D4/AMI (E&M WINK ONLY) PRI -Frame
Type: ESF/B8ZS or D4/AMISwitch Types: ATT 4ESS, ATT 5ESS, DMS100,
DMS250, and NI2NO support for Shared D-channels across multiple
PRIs (NFAS)Behind the PBX: (Your PBX T1 card must provide clock to
our system.) CAS -Frame Type: ESF/B8ZS or D4/AMI PRI -Frame Type:
ESF/B8ZS or D4/AMISwitch Types: ATT 4ESS, ATT 5ESS, DMS100, DMS250,
and NI2(Sonexis ConferenceManager can be either network- or client-
side.)DialPlan- Configure the dial plan on the PBX to route calls
to the Sonexis. Normally thisincludes associating an extension and
DID with the trunk group (be it T1, PRI or VOIP).General Notes: 1.
Customer must provide T1 straight through or crossover cable(s) to
connect SonexisConferenceManager to the PBX. Cable lengths in
excess of 133 feet require a CSU/DSU. 2. Sonexis ConferenceManager
only supports E&M Wink on CAS circuits and requires a
minimumWink duration of 200 milliseconds. 3. Sonexis
ConferenceManager DOES NOT support:a. Shared D-channels across
multiple PRIs (NFAS); orb. QSIG (Q Signaling).STAR Performance Kit
Pre-Implementation Site Requirements (05-28-09).DocPage 1 of 3 5.
VOIP systems:General VOIP considerations:The Sonexis transmits 20ms
RTP audio via G711. We support DSCP priority tagging,
expeditedforwarding.H.323 Sonexis ConferenceManager supports the
standard implementation of H.323., We support fast start and DTMF
via user information messages.SIP Sonexis ConferenceManager
supports the standard implementation of SIP. We support DTMF via
SIP INFO and RFC2833. DTMF payload type is configurable
96-105Bandwidth notation: Sonexis ConferenceManager currently
supports G711 which utilizes about 90kpbs per call in each
direction, or 180 kbps total per caller.Network Configuration: 1.
IP AddressesSonexis ConferenceManager requires a static IP address.
(A customer-specified,friendly HOST name is strongly recommended.)
Configure your Domain Name Server (DNS) sothat your network uses
the same domain name whether Sonexis Conference Manager is
accessedfrom inside or outside your network. This is required to
ensure that ConferenceManagersautomatic email invitations will
contain the correct URL for Web conferences. In addition,
SonexisConferenceManager will likely require a public IP address
for access outside your local areanetwork. This public IP address
can be assigned directly to the Sonexis ConferenceManager; oryou
may use 1-to-1 Network Address Translation (NAT) via a firewall or
router. 2. Operating System UpdatesDNS should be configured so that
your Sonexis ConferenceManagercan connect to Microsoft for updates
using the operating systems Automatic Updates utility.Updates
should be downloaded automatically and set to notify me when
downloads are ready toinstall. Since some updates require a system
restart, it is strongly recommended that thisoperation is performed
during non-business hours.STAR Performance Kit Pre-Implementation
Site Requirements (05-28-09).Doc Page 2 of 3 6. 3. Network
TopologyDetermine where the Sonexis ConferenceManager will reside
within yournetwork topology (i.e., behind the firewall or in a
DMZ), keeping in mind the security ramificationsof each
configuration. 4. Firewall Port ConfigurationSonexis
ConferenceManager requires the following firewall
portconfiguration: a.Port 80:Provides Web access to the system.
b.Port 8097: Provides administrative interface access. c. Port
9000, 9001-900x:Provides improved performance (optional). If this
feature is enabled, a number of ports (in the 9001-900x range)
equal to the anticipated number of simultaneous web conferences
must be opened. For example, ten simultaneous web conferences would
require ports 9000 and 9001-9010. 5. SSLTo use Sonexis
ConferenceManager over the Secure Sockets Layer (SSL), obtain a
securitycertificate prior to installation. The certificate can be
generated internally or obtained from acertificate provider (e.g.,
VeriSign). SSL requires access on port 443. Port 80 should be
closed.(Port 8097 will still be required for access to the
administrative interface.) 6. Automatic Email InvitationsSonexis
ConferenceManager can automatically send emailinvitations to
participants when conferences are scheduled. This functionality
requires thespecification of an SMTP mail gateway. Alternatively,
the SMTP server on the SonexisConferenceManager can be enabled and
configured to send mail directly from the server. 7. Virus
ProtectionA high quality antivirus program should be installed on
the SonexisConferenceManager. Virus definitions should be updated
regularly. The following directoriesshould be excluded from the AV
realtime scan: C:sonexis and C:Program FilesMicrosoft
SQLServerMSSQLDataImportant Note: Please read this document
carefully. Contact your PBX manufacturer or supportprovider to
obtain all of the required components for integration with the
Sonexis ConferenceManagerprior to your scheduled installation date.
Sonexis representatives will not configure your PBX.For additional
information please contact Sonexis Customer Care at (866) 676-6394
[email protected] Performance Kit Pre-Implementation
Site Requirements (05-28-09).Doc Page 3 of 3 7. DIGITAL
CIRCUITT1/CAS or ISDN/PRIInternalPhones PSTNPBX (w/ available T1
cards)TIE LINE Connections PRI or CAS ADMIN PORT: (Standard T1
X-8097 over cable)TERMINAL SERVICES Sonexis Conference1 Per
SPANENABLED ManagerSONEXIS CONFERENCE PSTN2U `
MANAGERConfiguration: Behind a PBX LAN Connection:External Web
Client10/100/1000(Can beMinimal Port required: connected via PORT
80 DMZ)(Can be configured to use SSL) Additional Ports: 9000 9001
thru 900x (for Application Sharing...optional)` INTERNETINTERNAL
LAN FIREWALLEDGE ROUTER`Internal Web Clients 8. DIGITAL
CIRCUITT1/CAS or ISDN/PRI Internal Phones PSTNPBX T1 Endpoint
(SMART JACK)DIGITAL CIRCUIT T1/CAS or ISDN/PRICSU / DSU (if
necessary)ADMIN PORT: 8097 TERMINAL SERVICES Sonexis
ConferenceENABLED ManagerSONEXIS CONFERENCEPSTN2U `
MANAGERConfiguration:Direct TDMLAN Connection: External Web
Client10/100/1000(Can beMinimal Port required: connected via PORT
80 DMZ)(Can be configured to use SSL) Additional Ports: 9000 9001
thru 900x (for Application Sharing...optional)` INTERNETINTERNAL
LANFIREWALL EDGE ROUTER`Internal Web Clients 9. Sonexis Conference
ManagerInternal VoIP ` Phones Configuration:SIP/H.323/TAPI
WAVInternal Web ClientsINTERNAL LAN` LAN Connection:
10/100/1000NOTE: Sonexis recommends that the bridgeand the PBX be
on the ADMIN PORT:same physical switch and8097 the the network
allow for`TERMINAL SERVICES Voice Prioritization.ENABLED Concerning
bandwidth, weonly support G.711 External Web Client Minimal Port
required: PORT 80SONEXIS CONFERENCE (Can be configured to use
MANAGER SSL) Additional Ports: 90002U 9001 thru 900x (for
Application Sharing...optional) INTERNET100/1000IP-PBX
ETHERNETSWITCH FIREWALLEDGE ROUTER 10. Avaya Solution &
Interoperability Test LabApplication Notes for Configuring
SonexisConferenceManager with Avaya IP Office using anISDN/PRI
trunk Issue 1.0 AbstractThese Application Notes describe the
procedure for configuring Sonexis ConferenceManagerto interoperate
with Avaya IP Office using an ISDN/PRI trunk.Sonexis
ConferenceManager is an in-house audio conferencing bridge that
eliminates thecostly pay-as-you-go fees of subscription-based
services, while setting new standards forsecurity and ease of use.
Sonexis ConferenceManager is designed to work within existingvoice
and data networks, and Sonexis ConferenceManager is available with
a fully integratedWeb conferencing optionInformation in these
Application Notes has been obtained through DevConnect
compliancetesting and additional technical discussions. Testing was
conducted via the DevConnectProgram at the Avaya Solution and
Interoperability Test Lab.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes 1 of 16SPOC 9/10/2011
2011 Avaya Inc. All Rights Reserved. Sonexis-IPO_PRI 11. 1.
IntroductionThese Application Notes describe the procedure for
configuring Sonexis ConferenceManager(herein referred to as
ConferenceManager) to interoperate with Avaya IP
Office.ConferenceManager is an in-house audio conferencing bridge
that eliminates the costly pay-as-you-go fees of subscription-based
services, while setting new standards for security and ease ofuse.
ConferenceManager is designed to work within existing voice and
data networks, andConferenceManager is available with a fully
integrated Web conferencing option.These Application Notes assume
that Avaya IP Office is already installed and basicconfiguration
steps have been performed. Only steps relevant to this compliance
test will bedescribed in this document. PRI line configuration in
IP Office Short Code for call route Incoming Call Route2. General
Test Approach and Test ResultsThe general test approach was to
place calls to and from ConferenceManager. The mainobjectives were
to verify the following: Inbound calls Outbound calls Hold / Resume
Call termination (origination/destination) Transfer (blind/consult)
Conference (client initiated/host initiated) DTMF ANI/DNIS2.1.
Interoperability Compliance TestingThe interoperability compliance
testing included features and serviceability tests. The focus ofthe
compliance testing was primarily on verifying the interoperability
betweenConferenceManager and Avaya IP Office.2.2. Test ResultsThe
test objectives were verified. For serviceability testing,
ConferenceManager operatedproperly after recovering from failures
such as cable disconnects, and resets ofConferenceManager and Avaya
IP Office.2.3. SupportTechnical support for the ConferenceManager
solution can be obtained by contacting Sonexis: URL
[email protected] Phone (866) 676-6394CRK; Reviewed:Solution
& Interoperability Test Lab Application Notes2 of 16SPOC
9/10/2011 2011 Avaya Inc. All Rights Reserved.Sonexis-IPO_PRI 12.
3. Reference ConfigurationFigure 1 illustrates the configuration
used in these Application Notes. The sample configurationshows an
enterprise with Avaya IP Office. Endpoints include an Avaya 1616-I
IP Telephone, a4625SW IP Telephone, and an Avaya 1416 Digital
Telephone on IP Office.Note: An Avaya S8300D Server and an Avaya
G450 Media Gateway were included to simulatePSTN calls. Figure 1:
Test Configuration of Sonexis ConferenceManagerCRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
3 of 16SPOC 9/10/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_PRI 13. 4. Equipment and Software ValidatedThe
following equipment and software were used for the test
configuration. Equipment Software/FirmwareAvaya IP Office 500 V2
7.0(12)Avaya IP Office Manager on Windows XP9.0(3)Professional 2002
with SP3Avaya S8300D Server w/ G450 Media Gateway6.0.1(used to
simulate PSTN calls)Avaya H.323 IP Telephones on IP Office4625SW
(H.323) 2.9.11616-I (H.323) 1.22Avaya 1416 Digital Telephone -Avaya
H.323 IP SIP Telephones on AvayaAura Communication Manager
(simulatingPSTN phones)9620 (SIP) 2.6.49630 (SIP) 2.6.49620 (H.323)
3.19630 (H.323) 3.19650 (H.323) 3.1Sonexis on Windows Server 2008
with SP 2 10.0CRK; Reviewed: Solution & Interoperability Test
Lab Application Notes4 of 16SPOC 9/10/20112011 Avaya Inc. All
Rights Reserved.Sonexis-IPO_PRI 14. 5. Configure Avaya IP
OfficeThis section describes the steps required for configuring
Avaya IP Office. During thecompliance test, a PRI line was utilized
between Avaya IP Office and ConferenceManager.The procedures
include the following areas: Verify PRI line Channels License
Configure PRI Line Create the static PRI line Configure a short
code to route calls through the PRI line Create an Incoming Call
Route for the Inbound PRI callsThese steps are performed from the
Avaya IP Office Manager.CRK; Reviewed: Solution &
Interoperability Test Lab Application Notes 5 of 16SPOC
9/10/20112011 Avaya Inc. All Rights Reserved. Sonexis-IPO_PRI 15.
5.1. Verify PRI Line Channels LicenseIP Office is configured via
the IP Office Manager application. Log into the PC running theAvaya
IP Office Manager application, and select Start All Programs IP
Office Manager to launch the Manager application. Select the proper
IP Office system if there aremore than one IP Office system, and
log in with the appropriate credentials.From the configuration tree
in the left pane, select License IP500 Universal PRI
(AdditionalChannels). Verify that the License Status field is set
to Valid.If a required feature is not enabled or there is
insufficient capacity, contact an authorized Avayasales
representative to make the appropriate changes.CRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
6 of 16SPOC 9/10/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_PRI 16. 5.2. Configure PRI LineFrom the configuration
tree in the left pane, click on Line, and select 5, which is a PRI
line, todisplay the PRI 24 (Universal) Line 5 screen in the right
pane. Select the PRI 24 Line taband provide the following
information: Switch Type Select NI2 using the drop-down menu.
During the compliance test, NI2 was utilized on both (IP Office and
ConferenceManager). Channel Allocation Select 231 (or 123) using
the drop-down menu. Framing Select ESF using the drop-down menu
Zero Suppression Select B8ZS using the drop-down menu Line
Signaling - Select CPE using the drop-down menu. The
ConferenceManager side was set to Network.CRK; Reviewed:Solution
& Interoperability Test Lab Application Notes7 of 16SPOC
9/10/2011 2011 Avaya Inc. All Rights Reserved.Sonexis-IPO_PRI 17.
Select the Channels tab to display channels. Select channels that
will be used and click the Editbutton. All 23 channels were
utilized during the test.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes8 of 16SPOC 9/10/2011
2011 Avaya Inc. All Rights Reserved.Sonexis-IPO_PRI 18. On the
Multiple Channel Edit screen, provide the following information:
Incoming Group Enter the incoming line, created in Section 5.2.
Outgoing Group Enter the outgoing line, created in Section 5.2.
Admin Select In Service using the drop-down menu.Click on the OK
button.CRK; Reviewed:Solution & Interoperability Test Lab
Application Notes 9 of 16SPOC 9/10/2011 2011 Avaya Inc. All Rights
Reserved. Sonexis-IPO_PRI 19. 5.3. Configure a Short Code to Route
Calls through the PRI lineSelect Short Code in the left panel.
Right click and select Add. Enter 77301; where extension77301 will
be routed to ConferenceManager, in the Code text box. Select Dial
for the Featurefield. Enter the Outgoing Group number created in
Section 5.2 for the Line Group Id field.Enter . for the Telephone
Number field. Use default values for all other fields. Click the
OKbutton.Note: When extension 77031 was dialed, the call routed
thru the PRI line 5.CRK; Reviewed:Solution & Interoperability
Test Lab Application Notes10 of 16SPOC 9/10/2011 2011 Avaya Inc.
All Rights Reserved. Sonexis-IPO_PRI 20. 5.4. Create an Incoming
Call Route for the Inbound PRI CallsSelect Incoming Call Route in
the left pane. Right-click and select New.Enter the following: Any
Voice for the Bearer Capability field. Enter the Incoming Group
number created in Section 5.2 in the Line Group Id field. Use
default values for all other fields.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes11 of 16SPOC 9/10/2011
2011 Avaya Inc. All Rights Reserved. Sonexis-IPO_PRI 21. Next,
navigate to the Destinations tab and enter . under the Destination
field.Click the OK button.After making the changes, click on the
floppy disk icon (not shown) to push the changes to theIP Office
system and have them take effectNote: Changes will not take effect
until this step is completed. This may cause a reboot ofAvaya IP
Office causing service disruption.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes 12 of 16SPOC 9/10/2011
2011 Avaya Inc. All Rights Reserved.Sonexis-IPO_PRI 22. 6.
Configure the Sonexis ConferenceManagerSonexis installs,
configures, and customizes the ConferenceManager application for
their endcustomers. Thus, this section only describes the interface
configuration, so thatConferenceManager can talk to Avaya IP
Office. By the request of Sonexis, the only codectested during the
compliance test was G.711MU.The procedures for setting up
ConferenceManager for a PRI line include the following areas:
Installing License Configure Telephony6.1. Install PRI Line
licenseLaunch a web browser, enter https://:8097 in the URL,and log
in with the appropriate credentials. Navigate to the License menu.
Enter an appropriatelicense for the PRI line in the New License Key
field.Click on the Apply button.Note: During the test, Sonexis
provide the licenses for PRI, H323 and PRI lines.CRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes13 of 16SPOC 9/10/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_PRI 23. 6.2. Configure TelephonySelect the Telephony
tab and provide the following information: Circuit Type Select ISDN
PRI using the drop-down menu. Switch Type Select NI2 using the
drop-down menu. Check on the Network Side box. Frame/Line Type
Select ESF/B8ZS using the drop-down menu.Click on the restart
telephony button.CRK; Reviewed: Solution & Interoperability
Test Lab Application Notes14 of 16SPOC 9/10/20112011 Avaya Inc. All
Rights Reserved. Sonexis-IPO_PRI 24. 7. Verification StepsThis
section provides the tests that can be performed to verify proper
configuration of Avaya IPOffice and ConferenceManager.7.1. Verify
Avaya IP OfficeFrom a PC running the Avaya IP Office Monitor
application, select Start All Programs IP Office System Status to
launch the application. From the Avaya IP Office SystemStatus
screen, select Trunks Line 5 from the left pane and verify the
trunk is Idle under theCurrent State field.8. ConclusionThese
Application Notes describe the procedures required to configure
SonexisConferenceManager to interoperate with Avaya IP Office
through a PRI trunk. SonexisConferenceManager successfully passed
compliance testing.9. Additional ReferencesThe following Avaya
product documentation can be found at http://support.avaya.com[1]IP
Office 7.0 Standard Version Installation, Issue 23k, May 2011,
Document Number 15-601042[2]IP Office Release 7.0 Manager 9.0,
Issue 26h, May 2011, Document Number 15-601011Sonexis product
documentation can be requested at the following
site:http://www.sonexis.com/access/index.asp?id=40&Program=DevConnectCRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
15 of 16SPOC 9/10/2011 2011 Avaya Inc. All Rights
Reserved.Sonexis-IPO_PRI 25. Avaya Solution & Interoperability
Test LabApplication Notes for Configuring SonexisConferenceManager
with Avaya IP Office using a SIP trunk Issue 1.0AbstractThese
Application Notes describe the procedure for configuring Sonexis
ConferenceManagerto interoperate with Avaya IP Office using a SIP
trunk.Sonexis ConferenceManager is an in-house audio conferencing
bridge that eliminates thecostly pay-as-you-go fees of
subscription-based services, while setting new standards
forsecurity and ease of use. Sonexis ConferenceManager is designed
to work within existingvoice and data networks and available with a
fully integrated Web conferencing optionInformation in these
Application Notes has been obtained through DevConnect
compliancetesting and additional technical discussions. Testing was
conducted via the DevConnectProgram at the Avaya Solution and
Interoperability Test Lab.CRK; Reviewed: Solution &
Interoperability Test Lab Application Notes 1 of 19SPOC
9/20/20112011 Avaya Inc. All Rights Reserved. Sonexis-IPO_SIP 26.
1. IntroductionThese Application Notes describe the procedure for
configuring Sonexis ConferenceManager(herein referred to as
ConferenceManager) to interoperate with Avaya IP
Office.ConferenceManager is an in-house audio conferencing bridge
that eliminates the costly pay-as-you-go fees of subscription-based
services, while setting new standards for security and ease ofuse.
ConferenceManager is designed to work within existing voice and
data networks, andConferenceManager is available with a fully
integrated Web conferencing option.These Application Notes assume
that Avaya IP Office is already installed and basicconfiguration
steps have been performed. Only steps relevant to this compliance
test will bedescribed in this document. SIP trunk configuration in
IP Office Short Code for call route Incoming Call Route2. General
Test Approach and Test ResultsThe general test approach was to
place calls to and from ConferenceManager. The mainobjectives were
to verify the following: Inbound calls Outbound calls Hold / Resume
Call termination (origination/destination) Transfer (blind/consult)
Conference (client initiated/host initiated) DTMF ANI/DNIS2.1.
Interoperability Compliance TestingThe interoperability compliance
testing included features and serviceability tests. The focus ofthe
compliance testing was primarily on verifying the interoperability
betweenConferenceManager and Avaya IP Office.2.2. Test ResultsThe
test objectives were verified. For serviceability testing,
ConferenceManager operatedproperly after recovering from failures
such as cable disconnects, and resets ofConferenceManager and Avaya
IP Office.2.3. SupportTechnical support for the ConferenceManager
solution can be obtained by contacting Sonexis: URL
[email protected] Phone (866) 676-6394CRK; Reviewed:Solution
& Interoperability Test Lab Application Notes 2 of 19SPOC
9/20/2011 2011 Avaya Inc. All Rights Reserved. Sonexis-IPO_SIP 27.
3. Reference ConfigurationFigure 1 illustrates the configuration
used in these Application Notes. The sample configurationshows an
enterprise with Avaya IP Office. Endpoints include an Avaya 1616-I
IP Telephone, a4625SW IP Telephone, and an Avaya 1416 Digital
Telephone on IP Office.Note: An Avaya S8300D Server and an Avaya
G450 Media Gateway were included to simulatePSTN calls. Figure 1:
Test Configuration of Sonexis ConferenceManagerCRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
3 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 28. 4. Equipment and Software ValidatedThe
following equipment and software were used for the test
configuration. Equipment Software/FirmwareAvaya IP Office 500 V2
7.0(12)Avaya IP Office Manager on Windows XP9.0(3)Professional 2002
with SP3Avaya S8300D Server w/ G450 Media Gateway6.0.1(used to
simulate PSTN calls)Avaya H.323 IP Telephones on IP Office4625SW
(H.323) 2.9.11616-I (H.323) 1.22Avaya 1416 Digital Telephone -Avaya
H.323 IP SIP Telephones on AvayaAura Communication Manager
(simulatingPSTN phones)9620 (SIP) 2.6.49630 (SIP) 2.6.49620 (H.323)
3.19630 (H.323) 3.19650 (H.323) 3.1Sonexis on Windows Server 2008
with SP 2 10.0CRK; Reviewed: Solution & Interoperability Test
Lab Application Notes 4 of 19SPOC 9/20/20112011 Avaya Inc. All
Rights Reserved. Sonexis-IPO_SIP 29. 5. Configure Avaya IP
OfficeThis section describes the steps required for configuring
Avaya IP Office. During thecompliance test, a SIP trunk was
utilized between Avaya IP Office and ConferenceManager.The
procedures include the following areas: Verify SIP trunk Channels
License Configure LAN interface Enable SIP Trunk Create the static
SIP line Configure SIP URI parameters for the SIP Line Configure
VoIP Parameters for the SIP Line Configure a short code to route
calls through the SIP trunk Create an Incoming Call Route for the
Inbound SIP callsThese steps are performed from the Avaya IP Office
Manager.CRK; Reviewed: Solution & Interoperability Test Lab
Application Notes 5 of 19SPOC 9/20/20112011 Avaya Inc. All Rights
Reserved. Sonexis-IPO_SIP 30. 5.1. Verify SIP Trunk Channels
LicenseIP Office is configured via the IP Office Manager
application. Log into the PC running theAvaya IP Office Manager
application, and select Start All Programs IP Office Manager to
launch the Manager application. Select the proper IP Office system
if there aremore than one IP Office system, and log in with the
appropriate credentials.From the configuration tree in the left
pane, select License SIP Trunk Channels to displaythe SIP Trunk
Channels screen in the right pane. Verify that the License Status
field is set toValid.If a required feature is not enabled or there
is insufficient capacity, contact an authorized Avayasales
representative to make the appropriate changes.CRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
6 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 31. 5.2. Configure LAN interfaceFrom the
configuration tree in the left pane, select System to display the
System screen in theright pane. Click the LAN1 tab. Under the LAN1
tab, select the LAN Settings sub-tab, andprovide IP Address and IP
Mask.CRK; Reviewed:Solution & Interoperability Test Lab
Application Notes 7 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights
Reserved. Sonexis-IPO_SIP 32. 5.3. Enable SIP TrunkUnder the LAN1
tab, select the VoIP sub-tab and check the SIP Trunks Enable box.
Click theOK button.Note: During the initial configuration of Avaya
IP Office, the LAN1 was configured as a privatenetwork (LAN) and
the LAN2 was configured as a public network (WAN). Avaya IP Office
cansupport SIP extensions on the LAN1 and/or LAN2 interfaces.
However, the compliance testused the LAN1 interface for a SIP trunk
termination.CRK; Reviewed: Solution & Interoperability Test Lab
Application Notes 8 of 19SPOC 9/20/20112011 Avaya Inc. All Rights
Reserved. Sonexis-IPO_SIP 33. 5.4. Create SIP Lines for a SIP
TrunkSelect Line in the left pane. Using the right mouse click,
select New SIP Line [not shown],and create a new Line Number. Enter
an appropriate domain on the ITSP Domain Name field,and check the
InService check box. During the compliance test, a SIP line (27)
was configured.CRK; Reviewed: Solution & Interoperability Test
Lab Application Notes 9 of 19SPOC 9/20/20112011 Avaya Inc. All
Rights Reserved. Sonexis-IPO_SIP 34. Select the Transport sub-tab,
and provide the following information: ITSP Proxy Address Enter the
IP address of the far-end SIP termination point. Layer 4 Protocol
Select UDP. Use Network Topology Info Select None.CRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes10 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 35. 5.5. Configure SIP URI Parameters for the SIP
LineSelect the SIP URI tab to configure SIP URI parameters for the
SIP Line. Click on the Addbutton.Select * for the Local URI,
Contact, and Display Name fields. Enter a unique number for
theIncoming Group and Outgoing Group fields. The Incoming Group
field will be used formapping inbound calls from the SIP trunk to
local stations. The Outgoing Group will be usedfor routing calls
externally via the Short Code configured in Section 5.7. Use
default values forall other fields. Click the OK button.CRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes11 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 36. 5.6. Configure VoIP Parameters for the SIP
LineSelect the VoIP tab to Configure VoIP parameters for the SIP
Line. For Compression Mode,select G.711 ULAW 64K, since
ConferenceManager only supports G.711MU. Check Re-inviteSupported
check boxes.Click the OK button.CRK; Reviewed: Solution &
Interoperability Test Lab Application Notes12 of 19SPOC
9/20/20112011 Avaya Inc. All Rights Reserved. Sonexis-IPO_SIP 37.
5.7. Configure a Short Code to Route Calls through the SIP
trunkSelect Short Code in the left panel. Right click and select
Add. Enter 77301; where extension77301 will be routed to
ConferneceManager, in the Code text box. Select Dial for the
Featurefield. Enter the Outgoing Group number created in Section
5.5 for the Line Group Id field.Enter [email protected] for the Telephone
Number field. Use default values for all other fields.Click the OK
button.Note: When extension 77031 was dialed, the call routed thru
the SIP trunk 27.CRK; Reviewed: Solution & Interoperability
Test Lab Application Notes13 of 19SPOC 9/20/20112011 Avaya Inc. All
Rights Reserved. Sonexis-IPO_SIP 38. 5.8. Create an Incoming Call
Route for the Inbound SIP CallsSelect Incoming Call Route in the
left pane. Right-click and select New.Enter the following: Any
Voice for the Bearer Capability field. Enter the Incoming Group
number created for the URI in Section 5.5 in the Line Group
Idfield. Use default values for all other fields.CRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes14 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 39. Next, navigate to the Destinations tab and
enter . under the Destination field.Click the OK button.After
making the changes, click on the floppy disk icon (not shown) to
push the changes to theIP Office system and have them take
effectNote: Changes will not take effect until this step is
completed. This may cause a reboot ofAvaya IP Office causing
service disruption.CRK; Reviewed:Solution & Interoperability
Test Lab Application Notes 15 of 19SPOC 9/20/2011 2011 Avaya Inc.
All Rights Reserved.Sonexis-IPO_SIP 40. 6. Configure the Sonexis
ConferenceManagerSonexis installs, configures, and customizes the
ConferenceManager application for their endcustomers. Thus, this
section only describes the interface configuration, so
thatConferenceManager can talk to Avaya IP Office. By the request
of Sonexis, the only codectested during the compliance test was
G.711MU.The procedures for setting up ConferenceManager for a SIP
trunk include the following areas: Installing License Configure
Telephony6.1. Install SIP Trunk licenseLaunch a web browser, enter
https://:8097 in the URL,and log in with the appropriate
credentials. Navigate to the License menu. Enter an
appropriatelicense for SIP trunk in the New License Key field.Click
on the Apply button.Note: During the test, Sonexis provide the
licenses for SIP, H323 and PRI trunks.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes 16 of 19SPOC 9/20/2011
2011 Avaya Inc. All Rights Reserved.Sonexis-IPO_SIP 41. 6.2.
Configure TelephonySelect the Telephony tab and provide the
following information: Dialout Gateway IP: Enter the far-end SIP
trunk termination point. During thecompliance test, it should be
the IP Office LAN1 IP address. DTMF Payload Type: Set the payload
type to 101Click on the restart telephony button.CRK; Reviewed:
Solution & Interoperability Test Lab Application Notes17 of
19SPOC 9/20/20112011 Avaya Inc. All Rights Reserved.
Sonexis-IPO_SIP 42. 7. Verification StepsThis section provides the
tests that can be performed to verify proper configuration of Avaya
IPOffice and ConferenceManager.7.1. Verify Avaya IP OfficeFrom a PC
running the Avaya IP Office Monitor application, select Start All
Programs IP Office System Status to launch the application. From
the Avaya IP Office SystemStatus screen, select Trunks Line 27 from
the left pane and verify the trunk is Idle under theCurrent State
field.8. ConclusionThese Application Notes describe the procedures
required to configure SonexisConferenceManager to interoperate with
Avaya IP Office through a SIP trunk. SonexisConferenceManager
successfully passed compliance testing.9. Additional ReferencesThe
following Avaya product documentation can be found at
http://support.avaya.com[1]IP Office 7.0 Standard Version
Installation, Issue 23k, May 2011, Document Number 15-601042[2]IP
Office Release 7.0 Manager 9.0, Issue 26h, May 2011, Document
Number 15-601011Sonexis product documentation can be requested at
the following
site:http://www.sonexis.com/access/index.asp?id=40&Program=DevConnectCRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
18 of 19SPOC 9/20/2011 2011 Avaya Inc. All Rights
Reserved.Sonexis-IPO_SIP 43. Avaya Solution & Interoperability
Test LabApplication Notes for Configuring SonexisConferenceManager
with Avaya IP Office using an H323trunk Issue 1.0AbstractThese
Application Notes describe the procedure for configuring Sonexis
ConferenceManagerto interoperate with Avaya IP Office using a H323
trunk.Sonexis ConferenceManager is an in-house audio conferencing
bridge that eliminates thecostly pay-as-you-go fees of
subscription-based services, while setting new standards
forsecurity and ease of use. Sonexis ConferenceManager is designed
to work within existingvoice and data networks and available with a
fully integrated Web conferencing optionInformation in these
Application Notes has been obtained through DevConnect
compliancetesting and additional technical discussions. Testing was
conducted via the DevConnectProgram at the Avaya Solution and
Interoperability Test Lab.CRK; Reviewed: Solution &
Interoperability Test Lab Application Notes 1 of 16SPOC 9/7/2011
2011 Avaya Inc. All Rights Reserved. Sonexis-IPOH323 44. 1.
IntroductionThese Application Notes describe the procedure for
configuring Sonexis ConferenceManager(herein referred to as
ConferenceManager) to interoperate with Avaya IP
Office.ConferenceManager is an in-house audio conferencing bridge
that eliminates the costly pay-as-you-go fees of subscription-based
services, while setting new standards for security and ease ofuse.
ConferenceManager is designed to work within existing voice and
data networks, andConferenceManager is available with a fully
integrated Web conferencing option.These Application Notes assume
that Avaya IP Office is already installed and basicconfiguration
steps have been performed. Only steps relevant to this compliance
test will bedescribed in this document. H323 trunk configuration in
IP Office Short Code for call route Incoming Call Route2. General
Test Approach and Test ResultsThe general test approach was to
place calls to and from ConferenceManager. The mainobjectives were
to verify the following: Inbound calls Outbound calls Hold / Resume
Call termination (origination/destination) Transfer (blind/consult)
Conference (client initiated/host initiated) DTMF ANI/DNIS2.1.
Interoperability Compliance TestingThe interoperability compliance
testing included features and serviceability tests. The focus ofthe
compliance testing was primarily on verifying the interoperability
betweenConferenceManager and Avaya IP Office.2.2. Test ResultsThe
test objectives were verified. For serviceability testing,
ConferenceManager operatedproperly after recovering from failures
such as cable disconnects, and resets ofConferenceManager and Avaya
IP Office.2.3. SupportTechnical support for the ConferenceManager
solution can be obtained by contacting Sonexis: URL
[email protected] Phone (866) 676-6394CRK; Reviewed:Solution
& Interoperability Test Lab Application Notes2 of 16SPOC
9/7/20112011 Avaya Inc. All Rights Reserved.Sonexis-IPOH323 45. 3.
Reference ConfigurationFigure 1 illustrates the configuration used
in these Application Notes. The sample configurationshows an
enterprise with Avaya IP Office. Endpoints include an Avaya 1616-I
IP Telephone, a4625SW IP Telephone, and an Avaya 1416 Digital
Telephone on IP Office.Note: An Avaya S8300D Server and an Avaya
G450 Media Gateway were included to simulatePSTN calls. Figure 1:
Test Configuration of Sonexis ConferenceManagerCRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
3 of 16SPOC 9/7/20112011 Avaya Inc. All Rights Reserved.
Sonexis-IPOH323 46. 4. Equipment and Software ValidatedThe
following equipment and software were used for the test
configuration. Equipment Software/FirmwareAvaya IP Office 500 V2
7.0(12)Avaya IP Office Manager on Windows XP9.0(3)Professional 2002
with SP3Avaya S8300D Server w/ G450 Media Gateway6.0.1(used to
simulate PSTN calls)Avaya H.323 IP Telephones on IP Office4625SW
(H.323) 2.9.11616-I (H.323) 1.22Avaya 1416 Digital Telephone -Avaya
H.323 IP Telephones on Avaya Aura Communication Manager (simulating
PSTNphones)9620 (SIP) 2.6.49630 (SIP) 2.6.49620 (H.323) 3.19630
(H.323) 3.19650 (H.323) 3.1Sonexis on Windows Server 2008 with SP 2
10.0CRK; Reviewed: Solution & Interoperability Test Lab
Application Notes4 of 16SPOC 9/7/2011 2011 Avaya Inc. All Rights
Reserved.Sonexis-IPOH323 47. 5. Configure Avaya IP OfficeThis
section describes the steps required for configuring Avaya IP
Office. During thecompliance test, a H323 trunk was utilized
between Avaya IP Office and ConferenceManager.The procedures
include the following areas: Configure LAN interface Enable H323
Gatekeeper Create the static H323 line Configure a short code to
route calls through the H323 trunk Create an Incoming Call Route
for the Inbound callsThese steps are performed from the Avaya IP
Office Manager.CRK; Reviewed: Solution & Interoperability Test
Lab Application Notes 5 of 16SPOC 9/7/2011 2011 Avaya Inc. All
Rights Reserved. Sonexis-IPOH323 48. 5.1. Configure LAN
interfaceFrom the configuration tree in the left pane, select
System to display the System screen in theright pane. Click the
LAN1 tab. Under the LAN1 tab, select the LAN Settings sub-tab,
andprovide IP Address and IP Mask.CRK; Reviewed:Solution &
Interoperability Test Lab Application Notes6 of 16SPOC 9/7/20112011
Avaya Inc. All Rights Reserved.Sonexis-IPOH323 49. 5.2. Enable H323
GatekeeperUnder the LAN1 tab, select the VoIP sub-tab and verify
the H323 Gatekeeper Enable box.Click the OK button.Note: During the
initial configuration of Avaya IP Office, the LAN1 was configured
as a privatenetwork (LAN) and the LAN2 was configured as a public
network (WAN). Avaya IP Office cansupport H323 extensions on the
LAN1 and/or LAN2 interfaces. However, the compliance testused the
LAN1 interface for a H323 trunk termination.CRK; Reviewed: Solution
& Interoperability Test Lab Application Notes 7 of 16SPOC
9/7/2011 2011 Avaya Inc. All Rights Reserved. Sonexis-IPOH323 50.
5.3. Create a Line for a H323 TrunkSelect Line in the left pane.
Using the right mouse click, select New H323 Line [not shown],and
create a new Line Number, using the drop-down menu. Enter an
appropriate IncomingGroup ID, Outgoing Group ID, Number of
Channels, Outgoing Channels, and VoiceChannels.During the
compliance test, a H323 line (25) was configured.CRK; Reviewed:
Solution & Interoperability Test Lab Application Notes 8 of
16SPOC 9/7/2011 2011 Avaya Inc. All Rights Reserved.
Sonexis-IPOH323 51. Select the VoIP Settings sub-tab, and provide
the following information: Gateway IP Address Enter the IP address
of the far-end H323 termination point. Compression Mode Select
G.711 ULAW 64K, using the drop-down menu. Supplementary Services
Select H450, using the drop-down menu. To work with
ConferenceManager, IP Office should select H450 as a Supplementary
Services to enable the fast start option. Check the following check
boxeso Enable Fast Starto Out of Band DTMF Make sure the Allow
Direct Media Path field is not checked. For the H323 trunk
solution, ConferenceManager only supports Shuffling Off (no direct
media path).Click on the OK buttonCRK; Reviewed: Solution &
Interoperability Test Lab Application Notes 9 of 16SPOC 9/7/2011
2011 Avaya Inc. All Rights Reserved. Sonexis-IPOH323 52. 5.4.
Configure a Short Code to Route Calls through the H323 trunkSelect
Short Code in the left panel. Right click and select Add. Enter
77301 in the Code field;where extension 77301 will be routed to
ConferneceManager. Enter . for the TelephoneNumber field. Enter the
Outgoing Group number created in Section 5.3 for the Line GroupId
field. Use default values for all other fields.Click on the OK
button.Note: When extension 77031 was dialed, the call routed thru
the H323 trunk 25.CRK; Reviewed: Solution & Interoperability
Test Lab Application Notes 10 of 16SPOC 9/7/2011 2011 Avaya Inc.
All Rights Reserved.Sonexis-IPOH323 53. 5.5. Create an Incoming
Call Route for the Inbound H323 CallsSelect Incoming Call Route in
the left pane. Right-click and select New.Enter the following: Any
Voice for the Bearer Capability field. Enter the Incoming Group
number created for the URI in Section 5.3 in the IncomingGroup Id
field. Use default values for all other fields.CRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes11 of 16SPOC 9/7/20112011 Avaya Inc. All Rights Reserved.
Sonexis-IPOH323 54. Next, navigate to the Destinations tab and
enter . under the Destination field.Click on the OK button.After
making the changes, click on the floppy disk icon (not shown) to
push the changes to theIP Office system and have them take
effectNote: Changes will not take effect until this step is
completed. This may cause a reboot ofAvaya IP Office causing
service disruption.CRK; Reviewed:Solution & Interoperability
Test Lab Application Notes 12 of 16SPOC 9/7/20112011 Avaya Inc. All
Rights Reserved.Sonexis-IPOH323 55. 6. Configure the Sonexis
ConferenceManagerSonexis installs, configures, and customizes the
ConferenceManager application for their endcustomers. Thus, this
section only describes the interface configuration, so
thatConferenceManager can talk to Avaya IP Office. By the request
of Sonexis, the only codectested during the compliance test was
G.711MU.The procedures for setting up ConferenceManager for a H323
trunk include the following areas: Installing License Configure
Telephony6.1. Install H323 Trunk licenseLaunch a web browser, enter
https://:8097 in the URL,and log in with the appropriate
credentials. Navigate to the License menu. Enter an
appropriatelicense for H323 trunk in the New License Key
field.Click on the Apply button.Note: During the test, Sonexis
provide the licenses for SIP, H323 and PRI trunks.CRK;
Reviewed:Solution & Interoperability Test Lab Application Notes
13 of 16SPOC 9/7/20112011 Avaya Inc. All Rights
Reserved.Sonexis-IPOH323 56. 6.2. Configure TelephonySelect the
Telephony tab and provide the following information: Dialout
Gateway IP: Enter the far-end H323 trunk termination point. During
thecompliance test, it should be the IP Office LAN1 IP address.
H.323 Type: Set the type to Definity, using the drop-down
menu.Click on the restart telephony button.CRK; Reviewed: Solution
& Interoperability Test Lab Application Notes14 of 16SPOC
9/7/2011 2011 Avaya Inc. All Rights Reserved. Sonexis-IPOH323 57.
7. Verification StepsThis section provides the tests that can be
performed to verify proper configuration of Avaya IPOffice and
ConferenceManager.7.1. Verify Avaya IP OfficeFrom a PC running the
Avaya IP Office Monitor application, select Start All Programs IP
Office System Status to launch the application. From the Avaya IP
Office SystemStatus screen, select Trunks Line 25 from the left
pane and verify the trunk is Idle under theCurrent State field.8.
ConclusionThese Application Notes describe the procedures required
to configure SonexisConferenceManager to interoperate with Avaya IP
Office through a H323 trunk. SonexisConferenceManager successfully
passed compliance testing.9. Additional ReferencesThe following
Avaya product documentation can be found at
http://support.avaya.com[1]IP Office 7.0 Standard Version
Installation, Issue 23k, May 2011, Document Number 15-601042[2]IP
Office Release 7.0 Manager 9.0, Issue 26h, May 2011, Document
Number 15-601011Sonexis product documentation can be requested at
the following
site:http://www.sonexis.com/access/index.asp?id=40&Program=DevConnectCRK;
Reviewed:Solution & Interoperability Test Lab Application
Notes15 of 16SPOC 9/7/20112011 Avaya Inc. All Rights Reserved.
Sonexis-IPOH323 58. 2011Avaya Inc. All Rights Reserved.Avaya and
the Avaya Logo are trademarks of Avaya Inc. All trademarks
identified by and are registered trademarks or trademarks,
respectively, of Avaya Inc. All other trademarks are theproperty of
their respective owners. The information provided in these
Application Notes issubject to change without notice. The
configurations, technical data, and recommendationsprovided in
these Application Notes are believed to be accurate and dependable,
but arepresented without express or implied warranty. Users are
responsible for their application of anyproducts specified in these
Application Notes.Please e-mail any questions or comments
pertaining to these Application Notes along with thefull title name
and filename, located in the lower right corner, directly to the
Avaya DevConnectProgram at [email protected];
Reviewed:Solution & Interoperability Test Lab Application Notes
16 of 16SPOC 9/7/20112011 Avaya Inc. All Rights
Reserved.Sonexis-IPOH323