Setting up an Obi 202 + Obiline in the UK (Draft)
ianobi:
I don't have an OBi202, but I've just simulated your setup using an OBi110 and an OBi1032. Either firmware has changed or I'm just getting senile and forgetful! It seems the "@" format is required.
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(602@192.168.1.23:5062)}
Set up fake OBi202 sp3 as follows:
Service Providers -> ITSP Profile C -> SIP -> ProxyServer : 127.0.0.1
Voice Services -> SP3 Service -> Enable : (checked)
Voice Services -> SP3 Service > X_InboundCallRoute: {>602:ph,ph2}
Voice Services -> SP3 Service -> AuthUserName : (any letters or numbers but not blank)
Voice Services -> SP3 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP3 Service -> X_ServProvProfile : C
Voice Services -> SP3 Service -> CallerIDName : Whatever
This works for me all the time.
Quote
Directly attached phone gives one ring, then it appears the 110 answers as well as forking the call.
That's very odd. Maybe its a symptom of the wrong setup. See how it goes with the new setup.
Mouse:
I think we discovered the same thing at the same time - see above!!!!
ianobi:
I was typing at the same time as you! If fake provider needed for sp4 use Profile D and change sp3 to sp 4 in last post.
I don't think this setup should add any delay. I wonder if echo is maybe an impedance matching problem between the OBi110 and line. Is there any echo when answering a call on the OBi110 Phone Port?
Mouse:
Quote from: ianobi on July 23, 2015, 08:30:51 am
I was typing at the same time as you! If fake provider needed for sp4 use Profile D and change sp3 to sp 4 in last post.
I don't think this setup should add any delay. I wonder if echo is maybe an impedance matching problem between the OBi110 and line. Is there any echo when answering a call on the OBi110 Phone Port?
The Obi 110 has less echo typically than the 202+Obiline, and a shorter delay echo, so the canceller copes well
This arrangement seems to create a long delay echo, though the canceller does seem to learn it. Or the jitter buffer reduces.
Echo always has an impedance matching element, in general it is not possible to match impedance exactly as they vary with frequency. But I cannot see how an additional one is being added here - the 110's behavior should be the operative one line-wise I would think, and the 202 phone-wise. The 101 and 202 phone impedances are identical. My line is challenging impedance-wise - I am 2-3 miles from the exchange.
What probably would introduce a further delay would be 1) an analog to digital conversion 2) adaptive jitter buffer starting. large. I think it must be 2. There is a star code to kill the jitter buffer for one call.
Mouse:
Quote from: Mouse on July 23, 2015, 08:47:07 am
Quote from: ianobi on July 23, 2015, 08:30:51 am
I was typing at the same time as you! If fake provider needed for sp4 use Profile D and change sp3 to sp 4 in last post.
I don't think this setup should add any delay. I wonder if echo is maybe an impedance matching problem between the OBi110 and line. Is there any echo when answering a call on the OBi110 Phone Port?
The Obi 110 has less echo typically than the 202+Obiline, and a shorter delay echo, so the canceller copes well
This arrangement seems to create a long delay echo, though the canceller does seem to learn it. Or the jitter buffer reduces.
Echo always has an impedance matching element, in general it is not possible to match impedance exactly as they vary with frequency. But I cannot see how an additional one is being added here - the 110's behavior should be the operative one line-wise I would think, and the 202 phone-wise. The 101 and 202 phone impedances are identical. My line is challenging impedance-wise - I am 2-3 miles from the exchange.
What probably would introduce a further delay would be 1) an analog to digital conversion 2) adaptive jitter buffer starting. large. I think it must be 2. There is a star code to kill the jitter buffer for one call.
Jitter seems likely from this 202 call status. It also seems to be repacketising, possibly because I have different RTP packet sizes set?
Terminal ID SP4 PHONE1
State connected connected
Peer Name
Peer Number 30184009
Start Time 16:50:33 16:50:33
Duration 00:00:07 00:00:07
Direction Inbound Inbound
Peer RTP Address 192.168.1.23:16804
Local RTP Address 192.168.1.21:17110
RTP Transport UDP
Audio Codec tx=G711A; rx=G711A
RTP Packetization (ms) tx=10; rx=20
RTP Packet Count tx=731; rx=365
RTP Byte Count tx=67252; rx=62780
Peer Clock Differential Rate 0 PPM
Packets In Jitter Buffer 5
Packets Out-Of-Order 0
Packets (10ms) Interpolated 0
Packets Late (Dropped) 0
Packets Lost 0
Packet Loss Rate 0 %
Packet Drop Rate 0 %
Jitter Buffer Length 90 ms
Received Interarrival Jitter 2 ms
DTMF Digits Received 0
Jitter Buffer Underruns 0
Jitter Buffer Overruns 0
Sequence number discontinuities 0
skew compensation 0 ms
send silence 0
MOS 4.42
Navigation
[0] Message Index
[#] Next page
[*] Previous page