Setting up an Obi 202 + Obiline in the UK (Draft)
Mouse:
Quote from: ianobi on July 23, 2015, 09:51:51 am
This has come up before in connection with sending pace maker data over a voip connection!
Quote
OBI200 ATA Unit – See http://www.obihai.com/OBiDeviceAdminGuide
Add a star code *99 as this:
*99, Modem Call, set($Noji1,200),set($Noec1,1),set($Cdm1,1),call(18002975493)
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
I think I'm going to need a beer later 8)
Indeed two beers, if not a barrel :) Can you do that for inbound as well?
(Thanks very much for all your help)
Mike
ianobi:
I think that the Star Code approach probably only works for the OBi2xx series. OBi1xx series is a definite no. I've just tried it using an OBi1032 and that does not work. However, with the OBi1032 it is possible to set the maximum jitter buffer length for each individual spX.
Ideas developed by azrobert and Mango seem to suggest that this format also works:
16042999000,Modem Call,set($Noji1,200),set($Noec1,1),set($Cdm1,3),call(16042999000)
In the relevant Star Code Profile / slot use the number to be dialled (16042999000 in this case) instead of an actual *99 type Star Code. I think that you would need to dial manually (not via a "send key") to allow the Star Code DigitMap(?) to pick up the number. That's needs some trials to prove and I don't have an OBI202 to try it out!
I don't know any way to influence jitter buffer length for incoming calls.
Mouse:
Quote from: ianobi on July 24, 2015, 03:40:18 am
I think that the Star Code approach probably only works for the OBi2xx series. OBi1xx series is a definite no. I've just tried it using an OBi1032 and that does not work. However, with the OBi1032 it is possible to set the maximum jitter buffer length for each individual spX.
Ideas developed by azrobert and Mango seem to suggest that this format also works:
16042999000,Modem Call,set($Noji1,200),set($Noec1,1),set($Cdm1,3),call(16042999000)
In the relevant Star Code Profile / slot use the number to be dialled (16042999000 in this case) instead of an actual *99 type Star Code. I think that you would need to dial manually (not via a "send key") to allow the Star Code DigitMap(?) to pick up the number. That's needs some trials to prove and I don't have an OBI202 to try it out!
I don't know any way to influence jitter buffer length for incoming calls.
Interesting indeed but unfortunately if it does not work on the 110 and does not work inbound from the LAN it probably won't allow the echo problem arising from linking the devices to be solved?
The main echo problem I have is on line 1, PSTN. As with many people I need inbound PSTN at reasonable quality and the Obiline 202, while better than an SPA 3102 is marginal. (Outbound can be all SIP except for emergencies). Still trying to decide if it is good enough. The 110 is better, but much more limited in other ways.
I have wondered if you can set any parameter in the Obiline (packet size, jitter buffer etc) as it must translate analog to digital in the Obline device, it must get those values from somewhere!!!!
Thank you very much indeed for all your kind help though.
Mike
Navigation
[0] Message Index
[*] Previous page