Obi-100 (or 202!) and Sipsorcery
user17600:
I've searched the forums and can't find the answer to my specific issue.
Background: I'm using Sipsorcery to aggregate 6 SIP providers, including several GV accounts. The dialplan is set up so that I dial an asterisk and a number between 1 and 9 (e.g., *2-555-444-1212) to indicate which account (trunk) I want the call to go out through. I'm currently using a Linksys ATA which is intermittently failing.
The Obi's use a similar convention to force the use of an account (trunk): **1, **2, etc. I'm pretty sure I read somewhere that the Obi's can be configured to change this behavior.
What I'd like to do is have the Obi trunk be driven by pound signs (#'s), or to separate the behavior of Obi and Sipsorcery in some manner. I'm open to pretty much any approach to address this issue.
Does anyone have this same setup, and how have you worked around this issue?
Many thanks.
ianobi:
This post may be of interest:
http://www.obitalk.com/forum/index.php?topic=701.msg4299#msg4299
user17600:
Thanks, Ian. Gives me a place to start.
Still, if anyone is successfully using Sipsorcery with an Obi unit, would appreciate a comment, or even a sample digitmap, and positive or negative experiences with an Obi/SS combo.
u1
pc44:
Hi user17600,
I think lhm. is the user you will want to hear from. Hopefully he will see this thread and respond. While I have used Sipsorcery in the past, I no longer rely upon it since the introduction of the OBi. In fact, the OBi was the reason I no longer need to use Sipsorcery. I still maintain an active account with them, but I would probably not be of any "real" help to you. All of those Ruby script edits are in my past now. :)
Here's a post by lhm. Also, if you search the forum for "sipsorcery" you should see several results.
pc44
user17600:
Super. Can't test the above link b/c I have a -110 right now and a leading # opens the POTS line, so looking for some confirmation before purchase.
Cheers
Navigation
[0] Message Index
[#] Next page