Setting up an Obi 202 + Obiline in the UK (Draft)

<< < (15/16) > >>

Mouse:
OK same packet size, now it is passed straight thru to 202. No call status.

Mouse:
Quote from: Mouse on July 23, 2015, 08:59:12 am

OK same packet size, now it is passed straight thru to 202. No call status.


Sorry my mistake picked up wrong phone!

Jitter is very high for a lan - what gives I wonder?

Problem remains:
Terminal ID   SP4   PHONE1
State   connected   connected
Peer Name      
Peer Number   30184009   
Start Time   17:02:33   17:02:33
Duration   00:00:05   00:00:05
Direction   Inbound   Inbound
Peer RTP Address   192.168.1.23:16806   
Local RTP Address   192.168.1.21:17118   
RTP Transport   UDP   
Audio Codec   tx=G711A; rx=G711A   
RTP Packetization (ms)   tx=10; rx=10   
RTP Packet Count   tx=548; rx=546   
RTP Byte Count   tx=50416; rx=50232   
Peer Clock Differential Rate   0 PPM   
Packets In Jitter Buffer   9   
Packets Out-Of-Order   0   
Packets (10ms) Interpolated   3   
Packets Late (Dropped)   1   
Packets Lost   3   
Packet Loss Rate   0 %   
Packet Drop Rate   0 %   
Jitter Buffer Length   90 ms   
Received Interarrival Jitter   10 ms   
DTMF Digits Received   0   
Jitter Buffer Underruns   1   
Jitter Buffer Overruns   0   
Sequence number discontinuities   3   
skew compensation   10 ms   
send silence   0   
MOS   4.40   
      

ianobi:
I just called from my OBi110 to my OBi1032 using direct ip to ip calling and got these results on same call:

OBi110
Jitter Buffer Length  170 ms
Received Interarrival Jitter  1 ms

OBi1032
Jitter Buffer Length 250 ms 
Received Interarrival Jitter 0 ms

Both devices are in the same lan subnet. Any query to Obihai normally gets the reply "the Jitter Buffer is fully adaptive to network conditions". I would expect my two devices in the same room as the router would be a pretty much perfect network! The OBi110 Jitter Buffer Length does slowly reduce, but I have never seen it below 120. The OBi1032 simply stays at 250 - I think there may need to  be some firmware tweaking on that one!

To be fair, call quality seems very high and MOS is good as it should be over a perfect network!

Mouse:
From manual:

$NOEC1 = Disable echo canceller once in the next call on this phone port (phone
-
port specific;
admissible
value: 1) (Not
available on OBi100/OBi110)

$NOJI1
= Disable jitter buffer adjustment once in the next call on this phone port (phone
-
port specific;
admissible
value: 1)
(Not available on OBi100/OBi110)

I am not sure if disabling the adjustment gets you a low value......

ianobi:
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)

Navigation

[0] Message Index

[#] Next page

[*] Previous page