Use of Trunk Group (TGn) for call route fallback

<< < (2/2)

lk96:
yep exactly, that's the feature I was looking for. And you worded it perfectly.

btw, I did consider using a single stage/two stage dialing by looping back calls through the obitalk network
(may be using a 2nd obi) so that I can use the forking capability of the inboundcallroute. But then
the setup gets convoluted and prone to errors as it involved more links and more obis. So I'm not
going to bother going that way.

btw2: have the Obi people ever consulted or supported any of the feature requests posted on that part
of this forum ?

L.

giqcass:
Quote

btw2: have the Obi people ever consulted or supported any of the feature requests posted on that part
of this forum ?

I got one of my feature request filled but it happened so quickly I believe they were working on it before I requested it.

ianobi:
Quote

btw2: have the Obi people ever consulted or supported any of the feature requests posted on that part of this forum ?

Sadly, not much evidence of that. However, I notice that Obihai now use the "Oleg Method" in some of their standard setups. I believe that they picked that up from this forum.

Shale:
Quote from: ianobi on July 06, 2013, 12:07:36 pm

Quote

btw2: have the Obi people ever consulted or supported any of the feature requests posted on that part of this forum ?

Sadly, not much evidence of that. However, I notice that Obihai now use the "Oleg Method" in some of their standard setups. I believe that they picked that up from this forum.

Most interesting.  They may not use the same method for each of their supported SIP providers. I look forward to doing some editing.

I just did a test. Indeed, when in the Expert Mode I undid the override on my OBiTalk Settings for my Anveo SP, the   X_InboundCallRoute was modified to the Oleg method. While I had put my own value there, the replacement value did not use the optional single quotes that I had used. I am not certain that copying the AuthUserName to the X_InboundCallRoute will work for every provider, but I expect OBi will determine that for each.

This is a really good development. The majority of users will no longer be plagued by SIP scanners. I made an interim change to http://www.obitalk.com/forum/index.php?topic=5467.0 to reflect this discovery.

Navigation

[0] Message Index

[*] Previous page