The SoundStructure VoIP Interface
12 - 75
dev_volt_neg_15 -14.9
dev_volt_clink 48.1
VoIP Plug-In Card 1
voip_board_info 3111-33215-001 Rev=2 Region=0,
MAC=00:04:F2:BF:00:1D
voip_bootblock_sw_ver 3.0.2.0391 (33215-001) 05-Aug-11 15:17
voip_bootrom_sw_ver 5.0.1.2999 16-Sep-11 07:05
voip_uc_sw_ver Mink 4.0.1.4394 16-Sep-11 06:41 file sip.ld
voip_dhcp_boot_serv static
voip_dhcp_boot_serv_opt 160
voip_dhcp_boot_serv_type string
voip_dhcp_option_60_type ascii_string
voip_eth_settings [mode] dhcp
voip_eth_settings [addr] 192.168.1.118
voip_eth_settings [dns] 192.168.1.1 0.0.0.0
voip_eth_settings [gw] 192.168.1.1
voip_eth_settings [nm] 255.255.255.0
voip_eth_vlan_id -1
voip_prov_serv_address 192.168.1.200
voip_prov_serv_type ftp
voip_prov_serv_user username
voip_status ok
Information Required for Support
Polycom’s Technical Support team is ready to help our integration partners
ensure their equipment is functioning properly. For specific questions regard-
ing integration with a VoIP PBX or call management platform, you should
contact the IT/Phone integration specialist in your organization or at your end
user’s installation.
Before calling Polycom Technical Support for assistance, Polycom recom-
mends that you have the following information:
• SoundStructure project file (.str extension).
This file allows the support team to understand the design and see if the
SoundStructure VoIP Interface is part of the project.
• SoundStructure device log (retrieved from the SoundStructure Studio
Wiring page)
This file allows the support team understand the versions of firmware and
other settings of the SoundStructure device.
• Whether you have been able to make a SIP URL call to another SIP device.
This helps separate baseline functionality questions from PBX integration
To Next Page
Loading...
Need help?
General
