Using Obi100 as a gateway for other Obi devices

<< < (3/3)

Zopa:
You know, you find the most obscure things while doing this troubleshooting. I went ahead and changed the AuthUserName from Obi100 to something I liked better, and everything stopped working. After about 30 minutes of scratching my head and rechecking everything, I found the issue to be with Anveo, where if you have a pure character based name, i.e. "Obi" it will fail with 503 CLI is invalid error. Adding a number to the name, i.e. "Obi1" fixes the issue. Go figure... Here is the post that made me figure it out. http://forum.sipsorcery.com/viewtopic.php?t=4635

PS could it have anything to do with xx. vs @@. discussion? Don't think so, as it gets to the provider, but it is peculiar nonetheless.

Zopa:
I think I recall now why I was using ';ui=12223334444' in my GV setup. I believe it was to pass along the Caller ID info to Anveo and beyond. Btw, is there a way to add it my setup without using a GV, or is it really the same exact thing as AuthUserName?

Navigation

[0] Message Index

[*] Previous page