Setting up an Obi 202 + Obiline in the UK (Draft)
Mouse:
Caller id
Caller id method and detect method, you have FSK
I and http://www.aoakley.com/articles/2008-01-08.php have one setting on the SPA:
Caller id method = ETSI FSK with PR(UK)
BUT Obi does not seem to have that option
Mouse:
Tones
There are detailed differences, between your Obi settings and mine and aoakley's but I guess these don't have functional impact.
WelshPaul:
Quote from: Mouse on July 20, 2015, 04:21:18 am
Just had a problem with an incoming call. It was from a standard format UK number (0207) that you cannot phone (its outgoing call only)
The number was passed through the Obi, and a ring request issued, but there was no ring, and the Obi seemed to hang up straight away:
11:39:10 From LI1() Fork to:
PH1
PH2
11:39:10 Ringing (PH1)
11:39:10 Ringing (PH2)
11:39:10 Call Ended
The same number tried again and this time the OBi rang the phones OK
Just wondered if there was a bug in the new 3 ms setting?
Kind regards
Mike
Always the possibility that there is an issue with the setting, after all they have modified it. ???
Quote from: Mouse on July 20, 2015, 04:42:33 am
Hmm on the SPA, PSTN Disconnect I had:
Detect PSTN Long Silence: no
Disconnect Tone - 400@-30,400@-30; 2(*/0/1+2)
And this page is similar: http://www.aoakley.com/articles/2008-01-08.php
With:
Detect PSTN Long Silence: no
Disconnect Tone - 400@-30,400@-30; 2(3/0/1+2)
I seem to remember that the simpler disconnect tone you have, though it accord with a UK standard, was found not to be what is actually used in the UK
But this may be memory failure.... :) Maybe it's a format difference.
Kind regards
Mike
This was all tested and discussed a long time ago between myself and Obihai.
If my memory serves me correct, Obihai devices didn't support some of the characters that were used in Linksys/Cisco syntax. Such as '*', of course this may have changed as new firmware has been released since then... I said may ;D
However, with no change logs there is no way to know. :-\
Quote from: Mouse on July 20, 2015, 06:02:10 am
Ring control
Also from: http://www.aoakley.com/articles/2008-01-08.php
Ring Validation Time: 256ms
Ring Indication Delay: 512ms
Ring Timeout: 640ms
On the SPA I had ring indication delay = 0 like you, and ring timeout of 128ms like you, but validation time of 256ms like aoakley
I am not sure how ring indication delay and ring delay (latter present only on the Obi) relate.
EDIT: I misread this sorry...
"On the SPA I had ring indication delay = 0 like you, and ring timeout of 128ms like you, but validation time of 256ms like aoakley"
What you say is indeed correct, those are the values used on the OBi?
I have not read this thread myself, might be of some help: https://www.obitalk.com/forum/index.php?topic=102.0
Quote from: Mouse on July 20, 2015, 06:12:49 am
Caller id
Caller id method and detect method, you have FSK
I and http://www.aoakley.com/articles/2008-01-08.php have one setting on the SPA:
Caller id method = ETSI FSK with PR(UK)
BUT Obi does not seem to have that option.
Again already discussed, OBihai stated that FSK(V.23) works the same way.
"British Telecom FSK
British Telecom (BT) in the United Kingdom developed their own standard, which wakes up the display with a line reversal, then sends the data as CCITT v.23 modem tones in a format similar to MDMF. It is used by BT, wireless networks like the late Ionica, and some cable companies. Details are to be found in BT Supplier Information Notes (SINs) 227 and 242; another useful document is Designing Caller Identification Delivery Using XR-2211 for BT from the EXAR website."
Quote from: Mouse on July 20, 2015, 06:17:36 am
Tones
There are detailed differences, between your Obi settings and mine and aoakley's but I guess these don't have functional impact.
What you have to remember is that not all devices take the same syntax strings, offer the same settings or name their parameters the same. If all manufacturers used the same dialplan, tones and ringtone syntax I wouldn't have grey hairs! ;)
Mouse:
Quote from: WelshPaul on July 20, 2015, 07:27:18 am
Quote from: Mouse on July 20, 2015, 04:21:18 am
Just had a problem with an incoming call. It was from a standard format UK number (0207) that you cannot phone (its outgoing call only)
The number was passed through the Obi, and a ring request issued, but there was no ring, and the Obi seemed to hang up straight away:
11:39:10 From LI1() Fork to:
PH1
PH2
11:39:10 Ringing (PH1)
11:39:10 Ringing (PH2)
11:39:10 Call Ended
The same number tried again and this time the OBi rang the phones OK
Just wondered if there was a bug in the new 3 ms setting?
Kind regards
Mike
Always the possibility that there is an issue with the setting, after all they have modified it. ???
Quote from: Mouse on July 20, 2015, 04:42:33 am
Hmm on the SPA, PSTN Disconnect I had:
Detect PSTN Long Silence: no
Disconnect Tone - 400@-30,400@-30; 2(*/0/1+2)
And this page is similar: http://www.aoakley.com/articles/2008-01-08.php
With:
Detect PSTN Long Silence: no
Disconnect Tone - 400@-30,400@-30; 2(3/0/1+2)
I seem to remember that the simpler disconnect tone you have, though it accord with a UK standard, was found not to be what is actually used in the UK
But this may be memory failure.... :) Maybe it's a format difference.
Kind regards
Mike
This was all tested and discussed a long time ago between myself and Obihai. If my memory serves me correct, Obihai devices didn't support some of the characters that were used in Linksys/Cisco stuff. Such as '*', of course this may have changed as new firmware has been released since then... I said may ;D
However, with no change logs there is no way to know.
Quote from: Mouse on July 20, 2015, 06:02:10 am
Ring control
Also from: http://www.aoakley.com/articles/2008-01-08.php
Ring Validation Time: 256ms
Ring Indication Delay: 512ms
Ring Timeout: 640ms
On the SPA I had ring indication delay = 0 like you, and ring timeout of 128ms like you, but validation time of 256ms like aoakley
I am not sure how ring indication delay and ring delay (latter present only on the Obi) relate.
The correct UK value is zero, back in 2006 I worked with somebody high up at BT and we came up with the correct UK values for use with Voipfone Linksys hardware.
Quote from: Mouse on July 20, 2015, 06:12:49 am
Caller id
Caller id method and detect method, you have FSK
I and http://www.aoakley.com/articles/2008-01-08.php have one setting on the SPA:
Caller id method = ETSI FSK with PR(UK)
BUT Obi does not seem to have that option
Again already discussed, OBIHAI have never added the option.
Quote from: Mouse on July 20, 2015, 06:17:36 am
Tones
There are detailed differences, between your Obi settings and mine and aoakley's but I guess these don't have functional impact.
What you have to remember is that not all devices take the same syntax strings, if all manufacturers used the same dialplan, tones and ringtone syntax I wouldn't have grey hairs! ;)
Thanks for our answers. Sorry where I am going over old ground, just double checking due to the missed call.
A quick look at the 2013 admin manual suggests that * is still not supported, and the other characters you need for: 400@-30,400@-30; 2(3/0/1+2) are supported except the '@-' becomes '-' but in field 3 -6 not 2. Field 2 takes the overall duration.
So 400-30,400-30; 2; 2(3/0/1+2) seems syntactically possible but may mean nothing or something different from on the SPA!
Kind regards
Mike
WelshPaul:
I just edited my post from my computer with some updated points, I originally posted from my mobile phone. ;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page