A Broadband and ADSL forum. BroadbanterBanter

Welcome to BroadbanterBanter.

You are currently viewing as a guest which gives you limited access to view most discussions and other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today.

Go Back   Home » BroadbanterBanter forum » Newsgroup Discussions » uk.telecom.voip (UK VOIP)
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

uk.telecom.voip (UK VOIP) (uk.telecom.voip) Discussion of topics relevant to packet based voice technologies including Voice over IP (VoIP), Fax over IP (FoIP), Voice over Frame Relay (VoFR), Voice over Broadband (VoB) and Voice on the Net (VoN) as well as service providers, hardware and software for use with these technologies. Advertising is not allowed.

Voxalot issues



 
 
Thread Tools Display Modes
  #1  
Old June 7th 07, 10:32 PM posted to uk.telecom.voip
Herman
external usenet poster
 
Posts: 100
Default Voxalot issues

A question for Brian methinks....

I am having issues with Voxalot outbound calls. My setup is a Fritzbox
configured with 10 SIP accounts with four or five providers, one of which is
a Voxalot account. I am trying to use Voxalot to route outbound calls, and
therefore also have these same accounts set up for outbound only (no
registration) on Voxalot. Nearly all outbound calls are routed from the
FritzBox to Voxalot. When I routed calls direct to the providers from the
FritzBox, everything worked fine.

The issue is that outbound calls over Voxalot are frequently failing
(generating SIP error 487 - call terminated). I have tested when calls
have been failing and some accounts may work over Voxalot (e.g. voip.co.uk)
while others don't (e.g. VCCom). There have been no SIP registration errors
at all for these accounts on the FritzBox. If I force the FritzBox to
re-register with Voxalot (by switching between the eu and us server, for
example) then everything works OK. Before you ask, yes I do also change the
server in Voxalot configuration.

I believe it could be the fact that I am registering the accounts on the
FritzBox for inbound, and routing the outbound calls via the same accounts
on Voxalot that is something to do with the issue. But the question is
whether anybody has experienced similar problems or could give some ideas as
to why exactly and what the solution is. I would like to keep inbound on my
FritzBox as I use different inbound diversion dependent on the account
(which Voxalot cannot do). I also want to keep outbound on Voxalot because
of the ability to modify dialstrings (e.g. for geo equivalents of NG
numbers).

Any ideas anyone? Am I going to have to put outbound and inbound through
the same "channel"? I would prefer to avoid this if poss. The only thought
I have is that maybe it is something to do with different ports being used
between Voxalot and FritzBox. All the accounts are set up for port 5060 on
Voxalot, but there is no possibility to influence (or know) the ports the
FritzBox uses.

--



  #2  
Old June 8th 07, 11:41 AM posted to uk.telecom.voip
Brian A
external usenet poster
 
Posts: 1,037
Default Voxalot issues

On Thu, 07 Jun 2007 20:32:25 GMT, "Herman"
wrote:

A question for Brian methinks....

I am having issues with Voxalot outbound calls. My setup is a Fritzbox
configured with 10 SIP accounts with four or five providers, one of which is
a Voxalot account. I am trying to use Voxalot to route outbound calls, and
therefore also have these same accounts set up for outbound only (no
registration) on Voxalot. Nearly all outbound calls are routed from the
FritzBox to Voxalot. When I routed calls direct to the providers from the
FritzBox, everything worked fine.

The issue is that outbound calls over Voxalot are frequently failing
(generating SIP error 487 - call terminated). I have tested when calls
have been failing and some accounts may work over Voxalot (e.g. voip.co.uk)
while others don't (e.g. VCCom). There have been no SIP registration errors
at all for these accounts on the FritzBox. If I force the FritzBox to
re-register with Voxalot (by switching between the eu and us server, for
example) then everything works OK. Before you ask, yes I do also change the
server in Voxalot configuration.

I believe it could be the fact that I am registering the accounts on the
FritzBox for inbound, and routing the outbound calls via the same accounts
on Voxalot that is something to do with the issue. But the question is
whether anybody has experienced similar problems or could give some ideas as
to why exactly and what the solution is. I would like to keep inbound on my
FritzBox as I use different inbound diversion dependent on the account
(which Voxalot cannot do). I also want to keep outbound on Voxalot because
of the ability to modify dialstrings (e.g. for geo equivalents of NG
numbers).

Any ideas anyone? Am I going to have to put outbound and inbound through
the same "channel"? I would prefer to avoid this if poss. The only thought
I have is that maybe it is something to do with different ports being used
between Voxalot and FritzBox. All the accounts are set up for port 5060 on
Voxalot, but there is no possibility to influence (or know) the ports the
FritzBox uses.

I don't, currently, have a Fritzbox so if there are any issues with a
Fritzbox/Voxalot tie up I can't comment.

There should be no problem in using unregistered , outgoing only,
providers providing those providers don't need to be registered. For
example some Australian providers state that they must be registered.

I assume that you have a dial plan on Voxalot. Have you tested all
number types, as you would dial them, or as they would be presented by
the Fritzbox, as appropriate, in the test box on the 'Providers'
page? Some people think that this will call a phone, it doesn't, it is
just to test out your dial plan. So, if you have not done this, try
out some typical numbers as you would dial them and see if they check
out OK. The result will be shown on the page after you have clicked on
'Test'. Sometimes there is a dial plan fault or a conflict between the
dial plan on the ATA and the dial plan on Voxalot. The order in which
the plan rules are placed, on Voxalot, can be important. Further, if
you do get a conflict it can sometimes be solved by setting the ATA
to insert characters, at the beginning of a dialled number type, then
stripping those characters off in the Voxalot dial plan.

As a further check, you could set up a speed dial on Voxalot and
choose a specific provider to route that call. Don't forget to allow
for speed dials in your Fritzbox plan (i.e. **xx for two digit speed
dials). If that works then change the route from the specific provider
to 'Dial Plan' and see if it still works. That way you can check out a
specific provider and your dial plan separately.

I hope this helps.
:-)
Remove 'no_spam_' from email address.

Sign petition to get High Definition TV via Freeview.
Ofcom want to auction off the spectrum needed for Hi Def
TV.
http://petitions.pm.gov.uk/High-Definition/
  #3  
Old June 8th 07, 08:25 PM posted to uk.telecom.voip
Herman
external usenet poster
 
Posts: 100
Default Voxalot issues

"Brian A" wrote in message
...
On Thu, 07 Jun 2007 20:32:25 GMT, "Herman"
wrote:

A question for Brian methinks....

I am having issues with Voxalot outbound calls. My setup is a Fritzbox
configured with 10 SIP accounts with four or five providers, one of which
is
a Voxalot account. I am trying to use Voxalot to route outbound calls,
and
therefore also have these same accounts set up for outbound only (no
registration) on Voxalot. Nearly all outbound calls are routed from the
FritzBox to Voxalot. When I routed calls direct to the providers from the
FritzBox, everything worked fine.

The issue is that outbound calls over Voxalot are frequently failing
(generating SIP error 487 - call terminated). I have tested when calls
have been failing and some accounts may work over Voxalot (e.g.
voip.co.uk)
while others don't (e.g. VCCom). There have been no SIP registration
errors
at all for these accounts on the FritzBox. If I force the FritzBox to
re-register with Voxalot (by switching between the eu and us server, for
example) then everything works OK. Before you ask, yes I do also change
the
server in Voxalot configuration.

I believe it could be the fact that I am registering the accounts on the
FritzBox for inbound, and routing the outbound calls via the same accounts
on Voxalot that is something to do with the issue. But the question is
whether anybody has experienced similar problems or could give some ideas
as
to why exactly and what the solution is. I would like to keep inbound on
my
FritzBox as I use different inbound diversion dependent on the account
(which Voxalot cannot do). I also want to keep outbound on Voxalot
because
of the ability to modify dialstrings (e.g. for geo equivalents of NG
numbers).

Any ideas anyone? Am I going to have to put outbound and inbound through
the same "channel"? I would prefer to avoid this if poss. The only
thought
I have is that maybe it is something to do with different ports being used
between Voxalot and FritzBox. All the accounts are set up for port 5060
on
Voxalot, but there is no possibility to influence (or know) the ports the
FritzBox uses.

I don't, currently, have a Fritzbox so if there are any issues with a
Fritzbox/Voxalot tie up I can't comment.

There should be no problem in using unregistered , outgoing only,
providers providing those providers don't need to be registered. For
example some Australian providers state that they must be registered.

I assume that you have a dial plan on Voxalot. Have you tested all
number types, as you would dial them, or as they would be presented by
the Fritzbox, as appropriate, in the test box on the 'Providers'
page? Some people think that this will call a phone, it doesn't, it is
just to test out your dial plan. So, if you have not done this, try
out some typical numbers as you would dial them and see if they check
out OK. The result will be shown on the page after you have clicked on
'Test'. Sometimes there is a dial plan fault or a conflict between the
dial plan on the ATA and the dial plan on Voxalot. The order in which
the plan rules are placed, on Voxalot, can be important. Further, if
you do get a conflict it can sometimes be solved by setting the ATA
to insert characters, at the beginning of a dialled number type, then
stripping those characters off in the Voxalot dial plan.

As a further check, you could set up a speed dial on Voxalot and
choose a specific provider to route that call. Don't forget to allow
for speed dials in your Fritzbox plan (i.e. **xx for two digit speed
dials). If that works then change the route from the specific provider
to 'Dial Plan' and see if it still works. That way you can check out a
specific provider and your dial plan separately.

I hope this helps.
:-)
Remove 'no_spam_' from email address.

Sign petition to get High Definition TV via Freeview.
Ofcom want to auction off the spectrum needed for Hi Def
TV.
http://petitions.pm.gov.uk/High-Definition/


Thanks Brian, something told me you'd be along soon.

The dialling rules are fine. 50% of the time there is no issue, and 50% of
the time there is.

As my main outbound provider (about 90% of calls) is VCCom (and I do not
have any inbound calls on this account) I have set this account up to
register now in Voxalot. Today I have had no issues, so I think there is
some sort of issue with splitting inbound and outbound in the way I did.
The question is what?

Could be something to do with Betamax IP address validation I guess? But
the only IPs involved are mine and those of the Voxalot server.


 




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Anyone having problems with Voxalot? Graham uk.telecom.voip (UK VOIP) 2 May 21st 07 01:28 AM
Voxalot {{{{{Welcome}}}}} uk.telecom.voip (UK VOIP) 26 October 13th 06 09:29 PM
Difference between Voxalot and SIPBroker? [email protected] uk.telecom.voip (UK VOIP) 3 September 6th 06 10:59 AM
BT BBV issues Duncan MacCallum uk.telecom.broadband (UK broadband) 5 July 2nd 04 05:09 PM


All times are GMT +1. The time now is 06:18 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.Content Relevant URLs by vBSEO 2.4.0
Copyright 2004-2019 BroadbanterBanter.
The comments are property of their posters.