VON OTN, Spring 2001
Testing notes - HearMe
HearMe joined nearly two-dozen leading VoIP venders to participate in the Open Test Network (OTN) at Spring 2001 VON in Phoenix, AZ. The participants met to publicly demonstrate the most advanced VoIP interoperability standards. HearMe demonstrated SIP interoperability with its SIP softphone (HearMe SoftPHONE™) and SIP and H.323 interoperability with its conferencing server (VoiceSERVER™). Below are the results of the many tests HearMe participated in.
Conferencing Testing
· HearMe’s Conferencing Server (VoiceSERVER™) was included in SIP and H.323 conferencing tests, as well as incoming Endpoint-to-Endpoint tests throughout the duration of the OTN. Utilizing SIP and H.323, various endpoints were directed to HearMe’s MCU (Multi-point Control Unit) to demonstrate its multi-party conferencing and SIP-H.323 bridging capabilities. HearMe successfully interoperated with the following devices: Indigo User Agents (SIP), Ubiquity User Agents (SIP), PingTel IP Phones (SIP), AdTech IP Phones (SIP, H.323) HearMe IP Softphone (SIP), Mockingbird gateway (SIP), Comgates Multi-Protocol Softswitch and Nuera Softswitch.
· HearMe’s SoftPHONE demonstrated its ability to place a call resolving the dialed telephone number to the IP Address of the device it was calling. Using SIP, the SoftPHONE properly signaled the target devices. The target devices answered the call and a full-duplex media path was established between them. HearMe successfully interoperated with the following target devices and Softswitches: Indigo User Agent (SIP), Ubiquity User Agent (SIP), PingTel IP Phones (SIP), AdTech IP Phones (SIP, H.323), Nortel IP Phones (SIP), Comgates Multi-Protocol Softswitch and Nuera Multi-protocol Softswitch.
·
HearMe’s SoftPHONE was provisioned with the IP
address of the REGISTRAR server. When the connection to the network was
established, the user agent client sent a “REGISTER” request to the REGISTRAR
server. The REGISTRAR server accepted an incoming request and put the device
into the location database. HearMe successfully interoperated with the
following companies’ Redirect and/or Proxy servers: Indigo, CommWorks and Ubiquity
·
HearMe’s SoftPHONE, acting as the originating
endpoint, submitted an “INVITE” request to the SIP redirect server. The
redirect server sent back a temporary move response to the originating endpoint
(Response code 302), and the SoftPHONE then acknowledged the change re-issuing
another “INVITE” message to the resolved entity. The terminating endpoint
acknowledged the “INVITE” messages, and a full duplex voice path was
established. HearMe successfully interoperated with the following companies’
Redirect and/or Proxy servers: Indigo, CommWorks and Ubiquity.
·
HearMe’s
SoftPHONE submitted an “INVITE” request to the outbound SIP proxy server. The
server performed routing lookup and issued an “INVITE” to the resolved
location. The termination endpoint accepted the connection, and a full duplex
voice path was established. HearMe successfully interoperated with the
following companies’ Redirect and/or Proxy servers: Indigo, CommWorks and Ubiquity.
·
HearMe’s SoftPHONE submitted an “INVITE” request
to the outbound SIP proxy server. The server determined that the request was
not for it’s authoritative domain and forwarded the request to another SIP
Proxy Server. The second SIP proxy server contacted the location server to
determine the final location of the endpoint. The termination endpoint accepted
the connection, and a full duplex voice path was established. HearMe
successfully interoperated with the following company’s Redirect/Proxy Server: Ubiquity
(outbound); Indigo and CommWorks (in-bound for the external domains).
Test Plan 17 - IP to Phone
(Peer-to-Peer)
·
After the telephone number was dialed, HearMe’s
SoftPHONE originated an “INVITE” method to place the call to the PSTN gateway.
The gateway acknowledged the “INVITE” message and routed the call for PSTN
termination. The call was completed and the SoftPHONE heard call progress tones
from the PSTN. HearMe successfully interoperated with the following company’s
SIP to PSTN Gateway: Mockingbird.
Test Plan 18 - Phone to IP
(Proxy Routed)
·
The incoming request was originated from PSTN by
dialing the number that would be terminated on a SIP PSTN Gateway. The gateway
asked the SIP Proxy to route the incoming request. The SIP proxy server queried
the location server to determine the proper location for the terminating
endpoint (HearMe’s SoftPHONE). When the endpoint location was resolved, the SIP
gateway sent an “INVITE” message to the terminating endpoint and a full duplex
voice communication between the originating PSTN caller and IP endpoint were
established. HearMe successfully interoperated with the following company’s SIP
to PSTN Gateway: Mockingbird. Outbound
proxy: Ubiquity.
·
HearMe’s SoftPHONE dialed a regular PSTN number.
Upon the receipt of the “INVITE” message, the Softswitch routed the call to the
responsible media gateway. The media gateway placed the call into PSTN and
acknowledged. A full duplex
communication between the originating endpoint and the PSTN destination was
established. HearMe successfully interoperated with the following companies’ Multi-Protocol
Softswitches: Comgates and Nuera.