triggering a callback without Obi answering the call
lk96:
I edited previous posting to correct the info that the Obi was not registering with Voxbeam actually.
Obitalk was saying one thing but when I went to the device itself it was giving me the real error.
L.
RonR:
Quote from: lk96 on January 21, 2012, 11:13:52 am
I dialed trying either the standard or premium access lines (ie 0011101 and 0011103 prefixes).
The Obi reports: Register Failed: 500 Method not allowed (server=95.211.119.251:5060; retry in 25s)
Have you listed your IP address at Voxbeam?:
Authentication
Authenticating your calls with Voxbeam couldn’t be simpler; all that we need to know is the IP address(es) that you’ll be sending calls from. You can add and remove IP addresses at any time using your Voxbeam account’s settings page.
Quote from: lk96 on January 21, 2012, 11:13:52 am
2. I'd like to simplify the dialed digits when using the Voxbeam trunk and to normalize the
dialing to that of other services (this is mostly for my other "customers" in the house that
have little tolerance for new dialing habits). So suppose I want the following:
if I dial on the handset **2 011 nn 1234567890 (nn=country code), the obi
converts it to appropriate # for the voxbeam trunk that will look like:
0011101 nn 1234567890
The following will prepend 0011101 to all calls sent using SP2:
Service Providers -> ITSP Profile B -> General -> DigitMap:
(<0011101>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|<011:>xx.)|(Mipd)|[^*#]@@.'@'@@.)
where aaa is your local (US) area code.
Stewart:
In addition to what RonR posted, please note:
1. Voxbeam will not accept a registration (there is no need, as they don't sell phone numbers or incoming service of any kind). So, if you put them in SP1 or SP2, turn off X_RegisterEnable for the service.
2. Voxbeam requires proper NAT mapping. In your setup, that does need STUN. Set STUNEnable and set a working STUN server in STUNServer (mine is currently set to stun.ekiga.net).
lk96:
Quote
Have you listed your IP address at Voxbeam?:
Yes, I had done that couple days back when I opened the Voxbeam account. And
verified that my public address matches the one I entered on my Voxbeam account.
Quote from: Stewart on January 21, 2012, 12:05:12 pm
In addition to what RonR posted, please note:
1. Voxbeam will not accept a registration (there is no need, as they don't sell phone numbers or incoming service of any kind). So, if you put them in SP1 or SP2, turn off X_RegisterEnable for the service.
Interesting they are doing strict checking. I have now disabled that option so
the Obi is not attempting to register.
Quote
2. Voxbeam requires proper NAT mapping. In your setup, that does need STUN. Set STUNEnable and set a working STUN server in STUNServer (mine is currently set to stun.ekiga.net).
I have done so as per your suggestion.
After taking care of all of the above, I still get "fast" rejection of any calls I try to make over
the SP2 trunk where I placed the Voxbeam account.
Any other ideas or things to check?
L.
Stewart:
Quote from: lk96 on January 21, 2012, 09:04:56 pm
After taking care of all of the above, I still get "fast" rejection of any calls I try to make over
the SP2 trunk where I placed the Voxbeam account.
Any other ideas or things to check?
Look at Call History, both for what error you got, and whether the correct number was sent to Voxbeam.
Navigation
[0] Message Index
[#] Next page
[*] Previous page