One stage dialling to remote OBi110's voice services in future firmware 1.3
yhfung:
Quote from: yhfung on March 23, 2011, 09:18:45 am
I am glad to see firmware 1.2 which has the one-stage dialling for remote OBi110 voice service.
However it seems that present method only applies to the primary voice service, right? If incorrect, please correct me.
<speed dial> + <*> + <number of the remote-OBi110 default primary voice service>
How to select other voice services which is not the primary voice service?
May I suggest to use the following method:
1) To access the default primary voice service
Same as above
2) To access the SP1 voice service
<speed dial> + <**1> + <number of the remote-OBi110 SP1 voice service>
3) To access the SP2 voice service
<speed dial> + <**2> + <number of the remote-OBi110 SP2 voice service>
4) To access the LINE port voice service
<speed dial> + <**8> + <number of the remote-OBi110 LINE port voice service>
5) To access OBiTalk voice service
<speed dial> + <**9> + <number of the remote-OBi110 OBiTalk voice service>
6) To access other voice service
<speed dial> + <**X> + <number of the remote-OBi110 other voice service>
The last should be defined by Obihai Technology later.
Does the future release of firmware version 1.3 have the above default Routes?
Since this provides more flexibility to the users. Besides the one-stage dialling for remote default line (trunk), other voice service can be accessed in a similar manner.
YH
asterisk@ck-lee.com:
I would agree that a simplified approach should be incorporated into the future firmware.
jimates:
Personally, I don't expect anything more from remote access than is available from the device itself.
IE:
direct dial for the default line from either place
press **? to access the other lines
Anything can be done from the callroute both locally and remotely.
yhfung:
jimates,
If there is no problem in two-stage dialling, we may use two-stage dialling to complete the call. However, if the remote Obi device is 10000km away from your local OBi device, there are problems in sending ANALOGUE DTMF numbers over 10000km, what can you do?
The answer to this problem is use ONE-STAGE DIALLING method (The digits sent are in the form of DIGITAL DTMF form rather than the anlogue form, the successful rate is ALWAYS 100%). The dialling methods are as follows:
Supposed the remote speed dial number is 2 via the COT, then the remote voice resources are
**1 : SP1
**2 : SP2
**8 : PSTN Line
**9 : ObiTalk
The default remote primary line (trunk) is set to PSTN Line
1) To access the remote default primary voice resource, i.e. PSTN Line
Dialling method: 2* + <remote PSTN Line telephone number>
2) To access the remote Obi SP1 voice resource
Dialling method: 2**1 + <remote SP1 number to be called>
3) To access the remote OBi SP2 voice resource
Dialling method: 2**2 + <remote SP2 number to be called>
4) To access the remote OBi PSTN voice resource (redundant but provided for logical thinking to make calls)
Dialling method: 2**8 + <remote PSTN Line number to be called>
5) To access the remote OBi OBitalk voice resource (redundant but provided for logical thinking to make calls)
Dialling method: 2**9 + <remote PSTN Line number to be called>
Since the remote OBi is belong to your COT, it is supposed that you are able access ALL remote OBi voice resources right?
In fact, I am able to accomplish this task by modifying the remote InBoundCallRoute of each voice resource. However I would like to make this feature to be the default settings in the firmware settings since most of the users know the logics but do not know how to modify the call routes.
With this added feature, most of users can easily access the remote sources WITHOUT any further modification to the call routes if this feature has been embebbded in the next firmware release.
YH
RonR:
yhfung,
Despite Obihai's statement to the contrary:
Quote from: OBi-Guru on March 11, 2011, 09:28:03 pm
Direct dialing from OBiON can only be directed to the Primary Line of the OBi gateway device.
jimates says his OBi supports **1, **2, **8, and **9 direct dialing:
Quote from: jimates on May 04, 2011, 08:56:40 pm
this is my Obitalk InboundCallRoute
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx):aa},{ph}
Calls from the 290xxxxxx (softphone number) accompanied by other digits are sent to sp1 or the ITSP profile (whatever), where they are again processed by the digitmap for that service.
if I dial **8, **1, **2 or **9; plus a valid number it is processed by the Obi the same as if dialed from the phone port.
without doing something like you proposed:
Quote from: yhfung on March 26, 2011, 03:50:55 am
With the firmware 1.2, it is able to make direct dial with OBiON app. However you have to modify the inbound calling rule in Voice Services > OBiTalk Service > InboundCallRoute：
{(caller OBi number)>(<*1:>xx.):sp1}|
{(caller OBi number)>(<*2:>xx.):sp2}|
{(caller OBi number)>(<*8:>xx.):li}|
{(caller OBi number)>(<*9:>xx.):pp}
such that it allows you to use the following format to make non-primary-line trunk:
<speed dial> + **1 + <sp1 number>
<speed dial> + **2 + <sp2 number>
<speed dial> + **8 + <LINE number>
<speed dial> + **9 + <OBiTalk number>
I can't find any evidence to support that named DigitMaps or OutboundCallRoutes are used to process InboundCallRoute rules such that **1, **2, **8, and **9 would be honored. The only way I can see it currently working is by using embedded DigitMaps as you outlined above.
Navigation
[0] Message Index
[#] Next page
[*] Previous page