Setting up an Obi 202 + Obiline in the UK (Draft)
Mouse:
Quote from: drgeoff on July 19, 2015, 03:49:43 am
Quote from: Mouse on July 19, 2015, 02:01:47 am
Quote from: Mouse on July 19, 2015, 01:43:04 am
Now trying packetsize of 10 ms and Line 1 TX gain = 0 -> -3 with compensatory DTMF gain -5 -> -2 to reduce echo and thus associated suppression activity.
Does not work. Its apparently not passing on DTMF even if I reduce TX gain only to -1, even with the compensation.
I am not sure DTMF playback level setting is working. Or maybe it works different from the SPA 3102.
My understanding of DTMF playback level is as follows but may be incorrect.
When DTMF tones are sent to your OBi out of band (ie in a side digital message, not tones in the coded speech path) your OBi reconstructs analogue DTMF tones to come out on the phone port. That parameter sets the level of those tones.
If the above is correct it will have no relevance to DTMF tones sent to a callee.
That does make sense of the observed behavior. Thanks for the feedback
Still strange that any adjustment in volume disables in band DTMF, reduces the value of the facility?
WelshPaul:
Quote from: Mouse
OK glad to have served that purpose :)
I also noticed that Obihai have changed the OnHookSpeed value from '3ms (ETSI)' to '3 ms (ETSI)' at some point. As a result if you uploaded any of the UK XML configuration files (v2.4 or lower) then this parameter will not have been altered from the devices default value.
I have updated the UK XML files... I have added the 'before first ring' value for the CallerIDTrigger parameter and updated the OnHookSpeed to reflect the new value of '3 ms (ETSI)'. I have also compared the XML output format against the very latest firmware release available at this time and all appears good again. :)
Mouse:
Quote from: WelshPaul on July 19, 2015, 07:21:24 am
Quote from: Mouse
OK glad to have served that purpose :)
I also noticed that Obihai have changed the OnHookSpeed value from '3ms (ETSI)' to '3 ms (ETSI)' at some point. As a result if you uploaded any of the UK XML configuration files (v2.4 or lower) then this parameter will not have been altered from the devices default value.
I have updated the UK XML files... I have added the 'before first ring' value for the CallerIDTrigger parameter and updated the OnHookSpeed to reflect the new value of '3 ms (ETSI)'. I have also compared the XML output format against the very latest firmware release available at this time and all appears good again. :)
That's great - I will change my guide above in the same way. Could someone move this post to Setup or UK Regional Board please
I also wondered if this setting should be changed - but I don't know what exactly it should be:
"To prevent delays in inbound ringing Set Physical Interfaces ~ Line Port ~ Ring Delay to 0. (If this causes problem with CLI you may need to increase this a bit say to 100 or 200)."
I worked with 0 for " Ring indication delay" on the SPA for years, so that may be right.
Kind regards
Mike
Mouse:
Thanks re 3ms ETSI. Now changed.
Mouse:
Quote from: WelshPaul on July 11, 2015, 01:56:08 am
You would of been better off posting this in the UK forum located at the bottom of the board. As for any delay or lost audio which can be replicated by dialling the above said number there is none. (For me)
Is the audio issue happening on calls placed over both OBiLINE and SIP calls?
On another note... There is no need to register your device with the OBiTALK portal if you're configuring the device locally.
Added ***6 method as an alternative to Obitalk firmware update.
Thanks for suggestion.... :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page