Board logo

標題: OBiApps to use OBi110 as voice gateway [打印本頁]

作者: ckleea    時間: 2011-4-8 06:30     標題: OBiApps to use OBi110 as voice gateway

In ObiApps, I can add an OBi110 as voice gateway. In the manual, it says, speed dial + * + tel  number will use the OBi110 to dial out.

I can do this but always via SP1 i.e. google voice line.

Is there any way to dial out via SP2 or PSTN?
作者: 角色    時間: 2011-4-8 07:26

本帖最後由 角色 於 2011-4-8 07:37 編輯

Yes, you are able to do it. The dialling method is show below:

<speed dial> + <*> + <tel number> (This goes to the primary trunk (line) of the callee for one-stage dialling using the speed dial method).

<speed dial> + <**1> + <tel number to SP1>
<speed dial> + <**2> + <tel number to SP2>
<speed dial> + <**8> + <tel number to PSTN>
<speed dial> + <**9> + <tel number to OBiTalk>

The caller with the firmware 1.2 or above will strip off the first "*" and send it to callee's primary trunk. If the default primary trunk of the callee is SP1, the caller's outgoing information will send to the SP1 via the SP1's inboundcallroute. As a result, the callee SP1 inboundcallroute should direct the caller's information to the corresponding trunk as follows:

{<*1> + <tel number to SP1>:sp1}
{<*2> + <tel number to SP2>:sp2}
{<*8> + <tel number to PSTN>:li}
{<*9> + <tel number to OBiTalk>:pp}

If your default for <speed dial> + <*> is PSTN trunk, you have to modify the inboundcallroute for the callee's PSTN trunk.


YH
作者: ckleea    時間: 2011-4-8 08:03

It does not work in my case.
作者: 角色    時間: 2011-4-8 09:07

You have to rewrite the inboundcallroute of the primary trunk of your OBi110 device. In your case, the default primary trunk is SP1.

YH
作者: bubblestar    時間: 2011-4-8 09:56

回復 3# ckleea


YH's explanation is correct.  I have been using this for voice gateway for almost 2 weeks without problem. The OBiAPP number has to be included in your Speed Dial list to make it work.

In your case, the OBiAPP is integrated into Asterisk now (using VNC and WINE way), the voice gateway dialing might not be the same as normal practice.  I think we have to figure out another way to fine tune the dial plan in Asterisk to accommodate OBiApps in this regard.
作者: ckleea    時間: 2011-4-8 10:08

回復 5# bubblestar


I still can't make it work. Will try later.

However, when I look at the call status screen when dialing, it shows up correctly as using SP1 or phone

There is an interesting follow up here at Obi forum

http://www.obitalk.com/forum/index.php?topic=604.0

I have removed the need of VNC and Gnome now.

VNC is just for checking the status.
作者: ckleea    時間: 2011-4-8 10:30

I got success now.

I modify the inbound callroute at Obitalk service as {>(xx.):li},{aa}

However, I would like to have a plan like this

2 - 9 xxxxxxx > line
1 xxx xxx xxx > SP1 (Google voice)

Please advise.
作者: ckleea    時間: 2011-4-8 11:21

I am using this but not working for SP1

{>(1xxxxxxxxx):sp1},{>([2-9]xxxxxxx):li},{aa}
作者: ckleea    時間: 2011-4-8 11:37

本帖最後由 ckleea 於 2011-4-8 11:40 編輯

Updated

Obitalk Service > InboundCallRoute
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(<**2:>xx.):sp2},{(290xxxxxx)>(<**8:>xx.):li},{(290xxxxxx):aa},{ph}

dialing 10 digits uses the default - sp1

dialing **2 + 10 digits uses sp2

dialing **8 + 10 digits uses the line
作者: 角色    時間: 2011-4-8 12:07

What is the result with the setting in 9#? Are you able to make it?

YH
作者: ckleea    時間: 2011-4-8 12:45

回復 10# 角色


    Only this {>([2-9]xxxxxxx):li},{aa} work for me.
作者: ckleea    時間: 2011-4-8 13:02

I got the right syntax now. It works for me as {>(<*1:>xx.):sp1},{>(<*2:>xx.):sp2},{>(<*8:>xx.):li},{>(<*9:>xx.):pp},{aa}

But since I use softclient via asterisk, it passes me different callerid. I have to figure a way to restrict the usage.

Thanks
作者: bubblestar    時間: 2011-4-8 13:31

回復 12# ckleea


   
For security sake, it is advised to let the authorized number to dial thru the gateway.  Your syntax seems to allow everyone to use the voice gateway now.
作者: 角色    時間: 2011-4-8 13:38

回復 12# ckleea
ck,

What is the function of the first right angle bracket (">") in your inboundcallroute {>(<*1:>xx.):sp1}, what happens if we change it to {(<*1:>xx.):sp1}?

YH
作者: ckleea    時間: 2011-4-8 13:47

I don't know. Initially it is bound by specific caller ID. But I am in a trust user environment and so I delete the 290xxxxxxx. It works.
作者: bubblestar    時間: 2011-4-8 14:42

> without preceding caller-list implies any number but anonymous.  Taking ckleea's first syntax as an example:

{>(<*1:>xx.):sp1} means any number but anonymous callers dialing *1 with 2 or more digits will go to and use service sp1.

It is equal to {@|?>(<*1:>xx.):sp1} where @=any number and ? = any number but anonymous.  The @|? preceding > can be omitted in this case.

However, ckleea's syntax might be that any callers who dials in can use sp1 service now.  If it is a pay-to-dial service, you'll know what the consequence is.
作者: bubblestar    時間: 2011-4-8 14:50

回復 15# ckleea


   
Trusted callers have to be explicitly included in your systax to avoid abusive dialing from other people.
作者: ckleea    時間: 2011-4-8 14:58

Kindly give more examples.

I have tried to put my number 290XXXXXXX but somehow it goes into aa or drop.

Don't know why
作者: bubblestar    時間: 2011-4-8 15:17

I remember that your CallerID service with Telephony company has not enabled yet.  Is this still the case? If yes, your OBi, of course, does not recognize your number even you are trusted.
作者: ckleea    時間: 2011-4-8 15:39

回復 19# bubblestar


    Yes, so for PSTN in, I default to go into password enabled SP2. But for the present discussion, I am using OBi110 from another OBiApp soft client.
作者: ckleea    時間: 2011-4-8 23:42

Have updated to allow trusted caller only.
Thanks for the advice




歡迎光臨 電訊茶室 (http://telecom-cafe.com/forum/) Powered by Discuz! 7.2