|
Voxalot Support Support for the Voxalot service. |
Thread Tools | Display Modes |
06-13-2009, 07:05 PM | #21 |
Senior Member
Join Date: Jul 2007
Location: Oregon, USA
Posts: 365
Thanks: 17 Thanked 77 Times in 64 Posts |
mathiasx,
When you forward your voip.ms DID to your Voxalot SIP URI, do you send it to voxalot.com (example: 123456@voxalot.com) or to a specific server (example 123456@proxy02.eu1.voxalot.com)? A clue about the problem might be obtained by calling your voip.ms SIP URI and reading the SIP packets returned from the voip.ms server. The packets can be captured using a packet monitoring program such as Wireshark. I can try this if you send me your voip.ms SIP URI. I have a voip.ms account myself but I don't have a DID there. I don't use it for incoming calls. After logging in, I did not immediately see any way to forward SIP URI calls from voip.ms to Voxalot without having a voip.ms DID. |
06-13-2009, 07:46 PM | #22 | |
Junior Member
Join Date: Aug 2007
Location: Germany
Posts: 12
Thanks: 0 Thanked 1 Times in 1 Posts |
Quote:
I send it to @voxalot.com as always. Martin had tested that before, he got a 484 error message. Regards, Mathias |
|
06-13-2009, 08:04 PM | #23 |
Senior Member
Join Date: Jul 2007
Location: Oregon, USA
Posts: 365
Thanks: 17 Thanked 77 Times in 64 Posts |
484 means Address incomplete (invalid number format). Apparently voip.ms does not have your complete Voxalot SIP URI.
|
06-13-2009, 08:20 PM | #24 |
Junior Member
Join Date: Aug 2007
Location: Germany
Posts: 12
Thanks: 0 Thanked 1 Times in 1 Posts |
Hi,
once again.... i have registered from voxalot to voip.ms, so i do not need to setup any sip uri at voip.ms. If the 484 is correct there is something wrong with the registration from voxalot to voip.ms (both sides stated as registered). And that's why i opend this thread (support request to voxalot). Regards, Mathias |
06-13-2009, 10:59 PM | #25 | |
Senior Member
|
It turns out that my problem was not related to incoming calls (or the new EU servers). It was to do with call forwarding, but the outgoing calls part. I made a change to my call plans recently which stopped the call forwarding from working. I have now corrected it, and all works fine. Incoming calls were actually never the problem. False alarm on my part. Sorry Martin
Quote:
__________________
http://www.planina.co.uk/contact.htm |
|
06-15-2009, 03:52 PM | #26 | |
Senior Member
Join Date: Jul 2007
Location: Oregon, USA
Posts: 365
Thanks: 17 Thanked 77 Times in 64 Posts |
Quote:
As I mentioned, I have a voip.ms account, which puts me in a position to help resolve the issue, but I am not going to do that unless asked because it could take a long time and there are plenty of fun things to do outdoors now that summer has arrived. Good luck. |
|