News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

USe 202 insterad of 200 for this application?

Started by Lavarock7, May 08, 2015, 08:24:23 AM

Previous topic - Next topic

Lavarock7

My Brother-in-Law has a pacemaker and his base unit sends updates a few times a month. The dialer model he uses has been reported as working with VOIP and they sent the following suggestions for an OBI-200.

---

Here are some setting were used by a patient with our Wave Communicator which has *99 capability. He programmed the OBi200 to use data-friendly settings upon a *99 command.  He also made some general changes to the OBi200.

The *99 command can be enabled on the Wave Communicator by setting the dipswitches 2 &3 up/on. You can contact us at 1.866.xxx.xxxx, option #1 if you need assistance with this step.

(Link to OBi Device Administration Guide)

Add a star code *99 as this:

*99, Modem Call, set($Noji1,200),set($Noec1,1),set($Cdm1,1),call(1800xxxxxxx)

The 3 set() commands tell the obi to do the following for the next outbound call:

1. Disable Jitter Buffer Adjustment, and use a fixed jitter buffer length of 200 ms
2. Disable Echo Canceller
3. Use only G711u codec

Change Codecs
G711U PacketizationPeriod = 10
G711A = Uncheck Enabled
G729 - Uncheck Enabled
G7296R32 - Uncheck Enabled

All other settings are OBI200 Default
Reboot OBIHAI Unit

---

Seems simple enough, however I wonder if it would be better to use an Obi-202 and hook this unit to phone 2. Then I could make permanent changes (like changing G711U on Codec Profile 2 permanently). I don't know if changing the codecs on the main profile might cause some issues with regular calls.

Also, if I do use the 202, can I default the other changes and not have to use the *99 command?

Anyone want to chime in on their opinion?
My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info<br />A simplified Voip explanation: http://voip.planet-aloha.com

OzarkEdge

#1
I like having the OBi202's extra phone port...

I don't see the jitter and echo parameters in the OBi web interface.  And their use of the jitter and codec vars is not documented in the admin guide, page 175, but maybe they work as they prescribe.  The codec could also be forced by disabling all but the desired codec?... the OBi202 can do this for just one phone port as you noted.

If the controls they prescribe are required and can only be set using a one shot star code, then the user must make the call by dialing the star code, and it won't matter what phone port he uses?  But having the OBi202's second codec profile would allow changing the PacketizationPeriod for just one port... you might prefer this isolation.

Maybe test all of this first using an existing OBi.

OE