January 04, 2022, 08:48:11 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Distinctive Ring with OBI (GV(1,3)->Asterisk(4)->OBI (Ph1,Ph2).....  (Read 4960 times)
lrosenman
Full Member
***
Posts: 237



« on: November 12, 2014, 02:03:58 pm »

I have an Obi 202, with 2 GV(SP1,SP3) accounts, Vitelity(SP2/e911, house number), and an Asterisk(FreePBX/IncrediblePBX, RaspberryPI) extension.  All calls coming in both GV lines go through Asterisk to do CNAM lookup.

Is there a way I can have the phones get different distinctive rings based on which of the 2 GV numbers was called?

Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4173


« Reply #1 on: November 12, 2014, 02:51:36 pm »

I assume you are routing calls from Raspbx back to the OBi202.
How are you routing calls back to the OBi202?
Do you have SP4 registered as a Raspbx extension?
Is SP2 outbound only?
Are you using both phone ports on the OBi202?

Ring Patterns are assigned to an SP.
You would have to route GV#1 calls to SP2 and GV#2 calls to SP4.
Logged
lrosenman
Full Member
***
Posts: 237



« Reply #2 on: November 12, 2014, 02:55:11 pm »

yes, the calls come back to the OBI on SP4 (a PBX extension).  I can *NOT* dedicate lines as you suggest, I.E. SP2 is the e911 / house line, and SP4 is the Asterisk.

Both PH1 and 2 are in use (PH1 is wireless DECT phones, and PH2 is my office Phone, and the Printer/fax machines).

Is there anything we can do on the Asterisk side to help here?

Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4173


« Reply #3 on: November 12, 2014, 03:10:06 pm »

You could route GV#1 calls to SP4 with ring pattern#1 assigned to SP4.
You could route GV#2 calls to SP2 via URI with ring pattern#2 assigned to SP2.
Logged
lrosenman
Full Member
***
Posts: 237



« Reply #4 on: November 12, 2014, 03:11:42 pm »

And what would be the settings on both the OBI and the Pi?
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 4173


« Reply #5 on: November 12, 2014, 04:05:15 pm »

OBi202
Assign a different ring pattern to SP4:
Voice Services -> SP4 Service
X_DefaultRing: Select a number (2-10) other than the default.

Voice Services -> SP2 Service
Add to the beginning of X_InboundCallRoute:
{>0:ph2},
This is only needed if you want to route GV calls differently than normal SP2 calls.
0 = number in the Raspbx extension Dial URI.

How do you route calls to Raspbx?
This is how I do it:
Voice Services -> SP3 Service -> X_InboundCallRoute:
sp2(200@192.168.1.100:5060;ui=$1)
200 = extn number
192.168.1.100:5060 = Raspbx IP address and port

Raspbx
Add Extension 200
Change Dial setting to: SIP/0@192.168.1.102:5061
192.168.1.102 is IP address of your OBi202
5061 points to SP2

Add an inbound route for extension 200

When you route calls to Raspbx via URI you need to define a dummy trunk with the OBi202 IP address, otherwise the call will be rejected.

Logged
lrosenman
Full Member
***
Posts: 237



« Reply #6 on: November 12, 2014, 04:40:02 pm »

I'm using a VoiceGateway to get from the OBI to Asterisk (FreePBX/IncrediblePBX), with a custom context.

it looks like:
Name: GV to Asterisk
Access Number: sp4(192.168.200.91)
Digit Map: (xx.)
AuthUserId: <valid ID>
AuthPassword: <valid Password>

And on SP1:
X_InboundCallRoute vg1(<GV ph# for GV1>/$1)

And on SP3:
X_InboundCallRoute vg1(GV Ph# for GV3>/$1)



then on the Asterisk side I have
defaultuser=<Valid user>
type=friend
secret=<valid password>
context=custom-from-Obihai
disallow=all
allow=ulaw
host=dynamic
dtmfmode=rfc2833
canreinvite=no
deny=0.0.0.0/0.0.0.0
permit=192.168.200.0/255.255.255.0


for the "dummy" trunk
and in extensions_custom.conf:
[custom-from-Obihai]
exten => _X!,1,Set(CALLERID(num)=${CUT(EXTEN,/,2)})
exten => _X!,n,Set(CALLERID(ani)=${CALLERID(num)})
exten => _X!,n,Goto(from-trunk,${CUT(EXTEN,/,1)},1)
exten => h,1,Macro(hangupcall,)

And then inbound routes for each GV that end with it going to ext 702 (the obi's extension)

so, ideas?
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement