WebRTC Outbound Calls

<< < (2/4) > >>

azrobert:
Quote from: Usetheforceobiwan on January 08, 2015, 06:17:40 pm

So in order to facilitate one stage dialing from non-login Getonsip calls,  you have to be prepared to permit one stage dialing for all calls inbound.

How do you pass an outbound number to the OBi with a non-login GetOnSip call?

Usetheforceobiwan:
Quote from: azrobert on January 08, 2015, 08:30:46 pm

I logged into my GetOnSip account for the above test.
My OBi call history shows my GetOnSip username as Peer Number.
I did not test for Peer Number in my testing.
I bridged all inbound calls out SP1, but since it shows in the call history I'm sure Peer Number can be tested for routing.



Tried pre-defined routing based on Peer Number being a Getonip user name i.e. {getsonsipusername:10#} and {getsonipusername:SPx(18005551212) and AA threw a 403 error upon redirect.  Wonder why?

Usetheforceobiwan:
Quote from: azrobert on January 08, 2015, 08:48:18 pm

Quote from: Usetheforceobiwan on January 08, 2015, 06:17:40 pm

So in order to facilitate one stage dialing from non-login Getonsip calls,  you have to be prepared to permit one stage dialing for all calls inbound.

How do you pass an outbound number to the OBi with a non-login GetOnSip call?


Actually as I edited my post to reflect you could not one stage dial through the Obi and  you cannot do second stage (i.e. Auto Attendant) dialing because the Getonsip web portal does not have a dial pad to generate the DTMF codes to tell the Obi Auto Attendent what to dial after you reach the attendant.  The best you can hope to do is be able to redirect a non-login GOS call by pre-defined redirect or in other words a hot line call.

azrobert:
Enabling X_SpoofCallerID can cause a 403 error.

Usetheforceobiwan:
Just tried to redirect using a non-login Getonsip call to my GOS Obi SP and I was able to route using {anonymous:LI(11235551212)} which bridged the call through the line port.  Audio worked fine both directions.  So it looks like you could setup a GV account on another SP, you could redirect to a pre-defined POTS number or directly to ph1 or ph2.  And if you have multiple GOS accounts, you could define as many Inbound route redirects as you have different GOS account names + an anonymous one for non-login GOS calls.

Navigation

[0] Message Index

[#] Next page

[*] Previous page