Howto:NeoTel SIP Provider Compatibility Test

From innovaphone-wiki

Jump to: navigation, search

Innovaphone Compatibility Test Report



The provider supports all required innovaphone features and is therefore qualified as recommended SIP Provider.

It does not support the G.723 codec. However this is a minor issue, because this codec is not used very often. The configuration on innovaphone side is simple, since the built-in SIP-GW can be used to connect to the provider.

NeoTel does not support the remote hold feature. When making a blind transfer(using redial key) the remote end will not get a MOH/dialtone from the provider.

The NeoTel support team was very fast and made an overall good impression.

That beeing said, NeoTel has achieved 92% of all possible test points. For more information on the test rating, please refer to Test Description

SIP Provider: NeoTel

  • Features:
    • Direct Dial In
    • DTMF
  • Supported Codecs by the provider
    • G711
    • G729
    • T.38

Current test state

The tests for this product have been completed.

Testing of this product has been finalized August 7th, 2008.

Testing Enviroment

Scenario NAT


This scenario describes a setup where the PBX and phones are in a private network. The IP800 must use a stun server, in order to send correct SIP - messages. The IP800 works as media relay, all RTP - streams go through the PBX.

Test Results

For more information on the test procedure, please read the following wiki article: SIP Interop Test Description. Bold lines in the test results indicate a KO-criteria.

Basic Call

Tested feature Result
call using g711a Yes
call using g711u Yes
call using g723 No
call using g729 Yes
Overlapped sending No
early media channel Yes
Fax using T.38 Yes
CGPN Can be supressed Yes
Reverse media negotiation Yes
Voice Quality OK? Yes

Direct Dial In

Tested feature Result
Inbound(Provider -> Innovaphone) Yes
Outbound(Innovaphone -> Provider) Yes


Tested feature Result
DTMF tones sent correctly Yes
DTMF tones received correctly Yes


Tested feature Result
Call can be put on hold Yes
Held end hears music on hold / announcement from PBX Yes
Held end hears music on hold / announcement from provider No

Transfer with consultation

Tested feature Result
Call can be transfered Yes
Held end hears music on hold Yes
Call returns to transferring device if the third

Endpoint is not available


Transfer with consultation (alerting only)

Tested feature Result
Call can be transfered Yes
Held end hears music on hold or dialing tone Yes
Call returns to transferring device if the third

Endpoint is not available


Blind Transfer

Tested feature Result S1
Call can be transfered Yes
Held end hears dialing tone No

Broadcast Group & Waiting Queue

Tested feature Result
Caller can make a call to a Broadcast Group Yes
Caller can make a call to a Waiting Queue Yes
Announcement if nobody picks up the call Yes


General Information

Firmware version

  • all innovaphone devices use 6.00 sr2-hotfix7 firmware

SIP - Trunk

First of all the SIP Trunk must be configured. Here an example of our NeoTel - Trunk. If you want that the Gateway should act as Medialrelay, you must exchange the Gatekeeper Address to an private network address; for example NeoTel awaits in the in the Preffered Identity Header the complete Calling Party Number(CGPN) or only the extension. .


Number Mapping

The complicated part on this issue is the correct mapping of the outgoing and incoming numbers.


Route Settings

Because NeoTel, as most SIP - Providers too, doesn't support overlap sending, you must enable the blockwise sending of the phone number. You can do this by enabling Force enblock in the automatically generated Routes.

The second setting you must check is Interworking(QSIG,SIP). This feature must be enabled to properly relay suplementary services, like Hold over the SIP Trunk. If this checkbox is unchecked only basic call Information like connect and disconnect will be forwarded by the Gateway.

Image:NeoTel SIP Compatibility Test 3.PNG

Media Relay

By enabling Media Relay on the PBX, The IP800 will work as an RTP - Proxy, so all RTP Streams will travel through the IP800. This mode poses a much greater load on the PBX, so the number of concurrent calls will be heavy limited.

Image:NeoTel SIP Compatibility Test 4.PNG

You may wonder about the usefullness of putting the localhost address as a private network. However you must insert this entry, if the IP800 SIP GW registers at the PBX on localhost interface.


The FAX was connected via a IP22 to the IP800. When configuring the IP22 you must keep in mind that you will use the analog interface for fax communication. Thats why the T.38 codec must be enabled.

Image:NeoTel SIP Compatibility Test 5.PNG

Now the PBX and the phones are setup correctly. You should be able to make call in both directions and send and receive fax messages.

Personal tools