Quote:
Originally Posted by michael77
it says registered on the sip adapter, and auth sent in voxalot web interface
|
| Aargh... despite having to type it several times below, it still somehow
| slipped my mind that ipkall isn't a regular VSP. The following details
| apply to registering with normal VSPs. Please see the instructions
| further below for how to get ipkall working. Sorry for the lunacy!
The problem is that the Auth Sent status means that Voxalot isn't yet registered with ipkall. At the risk of telling you something you may already know, allow me to step back a bit and try to explain how it is supposed to work for inbound calls:
Step 1. Set up your sip adapter to register with Voxalot. It appears that you have successfully done this (based on the fact that your sip adapter says registered). What this means is that Voxalot now knows that any inbound calls to your Voxalot number need to be sent on to your sip adapter (and hence your actual phone). You can test this by calling any one of the
global access numbers provided by SIP Broker and at the prompt, dial
*010xxxxxx where xxxxxx is your 6 digit Voxalot number. This should cause your phone to ring.
Step 2. Once your ATA is registered with Voxalot, you can then extend the chain by getting Voxalot to register (on your behalf) with your provider - ipkall in this instance. To do this, you need to enter your ipkall credentials into the
provider details on the Voxalot web site. By setting both the Active and SIP Register fields to Yes asks Voxalot to register with your provider. Once this is done successfully, then anyone calling your ipkall number will get routed to Voxalot (by ipkall), and then Voxalot will then reroute the call to your ATA and thus on to your actual phone.
The problem here is that the Voxalot->ipkall registration is in Auth Sent status. What this normally means is that whatever userid and password you have entered in the ipkall provider details in Voxalot are not recognized as being valid by ipkall. Can you confirm that the username and password that you entered in the ipkall provider details are your valid and correct ipkall credentials?
Sorry for the long winded post...
—
craig