DigitMap & OutboundCallRoute Help
drgeoff:
Quote from: scott818 on June 28, 2017, 04:20:11 pm
Quote from: drgeoff on June 28, 2017, 03:34:51 pm
The OutboundCallRoute is not an end in itself. You have not explained why you need, or think you need, the two 10 digit numbers 'to be referenced separately'.
Well let's say for example I wanted to ring number A and number B simultaneously. How could I "parse" number A and number B separately from OutboundCallRoute so I can do something like: SP1(number_A), SP1(number_B)? Is it even possible?
At the risk of someone else coming along and (metaphorically) chopping my head off, I'll stick my neck out and say that is not possible.
You can dial a first call and while it is active use a hook-flash and dial a second number. Hook flash again to have a 3-way call.
azrobert:
There is a hack you can use that "should" do what you want. The hack is looping a call out an SP trunk and back to the same device. You would route a 20 digit number out SP3 and SP4, looping it back to itself. In the SP3 inbound route you would send the 1st 10 digits to SP1 and in SP4 the 2nd 10 digits. This would require using OBi Expert to define a dummy trunk on SP3 and SP4, plus code to the digit map and out/inbound routes. I tested this looping a while ago and not for outbound calls, so I can't guarantee this will work. Let me know if you want to try this and I'll show you how.
Note: After one of the calls is answered the other call will end. You won't get a 3-way.
scott818:
Quote from: azrobert on June 29, 2017, 12:09:19 pm
There is a hack you can use that "should" do what you want. The hack is looping a call out an SP trunk and back to the same device. You would route a 20 digit number out SP3 and SP4, looping it back to itself. In the SP3 inbound route you would send the 1st 10 digits to SP1 and in SP4 the 2nd 10 digits. This would require using OBi Expert to define a dummy trunk on SP3 and SP4, plus code to the digit map and out/inbound routes. I tested this looping a while ago and not for outbound calls, so I can't guarantee this will work. Let me know if you want to try this and I'll show you how.
Yes! I would love to give that a try.
Quote from: azrobert on June 29, 2017, 12:09:19 pm
Note: After one of the calls is answered the other call will end. You won't get a 3-way.
That's fine. That's exactly the behavior that I want.
azrobert:
Service Providers -> ITSP Profile C SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile C SIP -> ProxyServerPort: 5063
Voice Services -> SP3 Service -> AuthUserName: loop1
Voice Services -> SP3 Service -> X_RegisterEnable: unchecked
Voice Services -> SP3 Service -> X_ServProvProfile: C
Voice Services -> SP3 Service -> X_InboundCallRoute:
{>(xxxxxxxxxx<xxxxxxxxxx:>):sp1},{sp1(6235941000)}
Service Providers -> ITSP Profile D SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile D SIP -> ProxyServerPort: 5062
Voice Services -> SP4 Service -> AuthUserName: loop2
Voice Services -> SP4 Service -> X_RegisterEnable: unchecked
Voice Services -> SP4 Service -> X_ServProvProfile: D
Voice Services -> SP4 Service -> X_InboundCallRoute:
{>(<xxxxxxxxxx:>xxxxxxxxxx):sp1},{sp1(6235941000)}
Physical Interfaces -> Phone1 or Phone2 Port -> DigitMap
Add after the beginning parenthesis: xxxxxxxxxxxxxxxxxxxx|
Physical Interfaces -> Phone1 or Phone2 Port
Add to the beginning of the OutboundCallRoute:
{(xxxxxxxxxxxxxxxxxxxx):sp3,sp4},
127.0.0.1 is a loopback address.
Calls out SP3 will loopback to SP4 and SP4 will loopback on SP3.
There is a reason I did this. If you want to know why, ask.
The call leg coming into SP3 will have the last 10 digits removed before routing to SP1.
The call leg coming into SP4 will have the first 10 digits removed before routing to SP1.
623-594-1000 is the number for Cox Communications and is for diagnostics. If for some reason the call doesn't match the inbound call route rule, it will be routed to Cox.
drgeoff:
Quote from: azrobert on June 29, 2017, 09:16:20 pm
Physical Interfaces -> Phone1 or Phone2 Port
Add to the beginning of the OutboundCallRoute:
{(xxxxxxxxxxxxxxxxxxxx):sp3,sp4},
That is interesting because the Admin Guide says (with my emphasis):
"Outbound Call Route Configuration
Every endpoint has an OutboundCallRoute parameter in the OBi device configuration. It tells the device where to send the call when the endpoint attempts to make a call. Endpoints may call each other or an outside number using one of the trunks. The OutboundCallRoute syntaxes are almost identical to those of the InboundCallRoute; the differences are mainly in the implied value when an optional field is omitted, no caller objects and one and only one terminal object per terminal-list in an OutboundCallRoute. Forking is not supported when routing outbound calls."
Navigation
[0] Message Index
[#] Next page
[*] Previous page