The UK's Number One VoIP Resource
This is a discussion on Re: voip.co.uk funnies again today? within the uk.telecom.voip forums, part of the Newsgroup Forums category; In an earlier contribution to this discussion, Linker3000 <linker3000@google-mailnohyphen.com> wrote: [color=blue] > Hi, at ...
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
In an earlier contribution to this discussion,
Linker3000 <linker3000@google-mailnohyphen.com> wrote: [color=blue] > Hi, at around noon today (Friday) one of our voip.co.uk numbers > started to give out 'This number is not in service' to all callers. I > couldn't get any sense from their support line (left msg - no > replies). The voip number was taking inbound calls diverted to it > from a 'regular' landline number and I 'fixed' the problem by > diverting calls to another voip.co.uk number terminating at the same > Asterisk server. > I have just dialled the 'faulty' number and its OK again, but I am > getting edgy now that voip.co.uk appears to have had a third glitch > in a few weeks - especially since they have had a pretty good record > up 'til recently. > > Anyone else?[/color] An intermittent fault would be an improvement for me! After over a month, both of my voip.co.uk-allocated 01926 numbers are *still* unable to take incoming calls (indicating not in service) from BT fixed line phones or mobile phones (Orange at any rate - dunno about others). They seem to be no nearer to fixing it. They accept it is a routing problem, and nothing to do with my setup (because I can receive voip calls from their network, and even calls made via the likes of 18866/1899) but they seem to be incapable of fixing it! -- Cheers, Roger ______ Email address maintained for newsgroup use only, and not regularly monitored.. Messages sent to it may not be read for several weeks. PLEASE REPLY TO NEWSGROUP! |
|
|||
|
Roger Mills expressed precisely :[color=blue]
> In an earlier contribution to this discussion, > Linker3000 <linker3000@google-mailnohyphen.com> wrote: >[color=green] >> Hi, at around noon today (Friday) one of our voip.co.uk numbers >> started to give out 'This number is not in service' to all callers. I >> couldn't get any sense from their support line (left msg - no >> replies). The voip number was taking inbound calls diverted to it >> from a 'regular' landline number and I 'fixed' the problem by >> diverting calls to another voip.co.uk number terminating at the same >> Asterisk server. >> I have just dialled the 'faulty' number and its OK again, but I am >> getting edgy now that voip.co.uk appears to have had a third glitch >> in a few weeks - especially since they have had a pretty good record >> up 'til recently. >> >> Anyone else?[/color] > > An intermittent fault would be an improvement for me! After over a month, > both of my voip.co.uk-allocated 01926 numbers are *still* unable to take > incoming calls (indicating not in service) from BT fixed line phones or > mobile phones (Orange at any rate - dunno about others). They seem to be no > nearer to fixing it. They accept it is a routing problem, and nothing to do > with my setup (because I can receive voip calls from their network, and even > calls made via the likes of 18866/1899) but they seem to be incapable of > fixing it![/color] I had the same issue. The fix was nothing to do with the ITSP. I ultimately had to report faults to each network that I was having difficulty placing the calls through. Have you reported the issue to Orange? I eventually got a call from NTL who said they'd fixed it, after I reported the fault to Orange. Make sure you don't mention the VoIP word to Orange, simply report having difficulty reaching an 01926 number. |
|
|||
|
Jono wrote:[color=blue]
> Roger Mills expressed precisely :[/color] [color=blue][color=green] >> An intermittent fault would be an improvement for me! After over a >> month, both of my voip.co.uk-allocated 01926 numbers are *still* >> unable to take incoming calls (indicating not in service) from BT >> fixed line phones or mobile phones (Orange at any rate - dunno about >> others). They seem to be no nearer to fixing it. They accept it is a >> routing problem, and nothing to do with my setup (because I can >> receive voip calls from their network, and even calls made via the >> likes of 18866/1899) but they seem to be incapable of fixing it![/color] > > I had the same issue. The fix was nothing to do with the ITSP. > > I ultimately had to report faults to each network that I was having > difficulty placing the calls through. Have you reported the issue to > Orange? I eventually got a call from NTL who said they'd fixed it, after > I reported the fault to Orange. > > Make sure you don't mention the VoIP word to Orange, simply report > having difficulty reaching an 01926 number.[/color] The network block owner (or their hosting operator) should have requested that the operators build the range anyway. Of course the operators do not have to heed this request though. The previous post suggests that the range is not diallable from BT landlines. Assuming that there is no CPS/IDA etc interfering here it suggests that the range has not been built by BTwholesale, which will be a large part of the problem. There may be upto 3 months lead time for this to be built by BT once the request goes in. There is a chance that the range has been built by BT but this is a fault, or that the "BT landlines" are actually using another operator to route calls and it is these operators who have not built the range on their networks. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|