We have a couple of Orcon VoIP lines that will not seem to accept a redirection from another number.


Background:


We have an Orcon business plan on the Orcon+ network (Wellington Central). We are using the Orcon homehub (Siemens Gigaset), and have two Orcon VoIP lines running off this.


We also have a 2talk number set up as an auto attendant (i.e. Hello, welcome to X. Please press 1 for ABC and 2 for DEF). This used to redirect to 2talk VoIP lines.


However we shifted our broadband to Orcon, and had all sorts of trouble using the Linksys router that was driving the 2talk VoIP lines. We ended up shifting to the Orcon homehub box, and to get the VoIP calling, had to use Orcon services. So the 2talk auto attendant now redirects to the two Orcon numbers (all local calls, not 028).


Problem:


This has worked well for the last month or so with no issues. Within the last day troubles have arisen. Dialling the 2talk number still reaches the auto attendant without trouble, but now pressing 1 or 2 (the redirect to the Orcon lines), about two-thirds of the time we get a message "Your call cannot be connected at this time. Please contact your service provider." Occassionally (not clear why - just to make me think that I have fixed it!?) the redirect works fine and the call goes through.


However direct dialling the Orcon numbers still goes through no troubles.


I am almost positive this is a problem with the Orcon numbers however. For our autoattendant, options 3 and 4 are to go through to Vodafone cell phones (we pay the costs of this), and that redirection works every time.


As I say, the set up worked really well for the last month or so. The only thing that has changed is that yesterday afternoon, we set up the voicemails on the Orcon lines. I was surprised that this would do anything, but is the only thing I can think of that's changed. We've tried resetting the voicemails ourselves, and had Orcon do it from their end. No luck.


We have also tried resetting the 2talk settings and the router a couple of times. No sustained success.


We've tried getting Orcon on this, and they basically don't want to know.


Any bright ideas as to what may be causing this issue? Otherwise we will be terminating our contract with Orcon.