Hi,
I've tried logging a few faults regarding this but have had no results... could someone at WXCH please tell me why I'm unable to receive calls from telstra clients to my 09 440XXXX ported number.
Thanks
Barry
Trusted
|
Trusted
Trusted
WorldxChange
Trusted
Trusted WorldxChange
jpollock: See, personally, if I was WorldXChange, I'd be raising hell on any shared technical groups... Perhaps the numbering plan people?
Because... Why would I want to have a WorldXChange account if people couldn't call the number? Would that increase or decrease the plan's value for a business? I would expect it would drop the value of the account to near 0.
So, we've got a situation where:
1) The TCL customers don't care, they call the mobile.
They do care, same way as our customers care if they couldn't call a number
2) TCL doesn't care, they aren't getting any complaints from their customers.
As above they will complain to TCL if you can't make calls
3) WorldXChange doesn't appear to care (mistakenly so), they say call TCL.
Sorry Jason absolutely wrong here and you should know better than that, we do care (alot) but you are missing the point we can not log a Fault on behalf of a TC customer, same way as they someone from TC could not log a fault with us directly for your Number , We have / They have no authorisation, if the TC customer logs a fault with TC they are obligated to check it out and will find most probably that in this case they have stuffed the porting up in a Switch load , generally this is quicker than us trying to go through our carrier contacts.
4) The guy that does care can't do anything about it.
Well, actually, he can...
I agree he can, help us to help him by getting the TC customers to ring TC and tell them they can't ring his number, also asked him to supply me his details so I can go through the carrier side , this may take longer though, Also TC will not take any faults from our helpdesk people as I say again, we have no Authorisation to act on a TC customers behalf , the amount of trouble we and they could get into if TC acted on a request from us..... then there would a thread war damning us all to hell.... damned if we do damned if we don't.
We seem to be seeing a heck of a lot routing issues between carriers since NP came in.
I agree, make no mistake here NP is actually a very very tricky business and some carriers do it better than others, some seem to be downright terrible it, but when you know what is actually involved with data manipulation, switch loads, databases it is a very very complicated process, it works well for some people but it requires every carrier to do the Job right across all platforms, if one part fails then some people will be effected and in this case I'm picking TC have an issue
I think this shows that there is a gap in the fault resolution processes in the NZ telecommunications market. Are there any call completion SLAs?
Yes there are, but these kinds of issue's probably do not show up, because it could be effecting only a small minority of customers, in this case possibly TC customers in one local area because the switch load details are missing for this customers number port.
Trusted
1) The TCL customers don't care, they call the mobile.Ah, but not enough to complain, which is the same thing. Is it a fault if no one reports it? Not on most quality system stats. ;)
They do care, same way as our customers care if they couldn't call a number
2) TCL doesn't care, they aren't getting any complaints from their customers.Except that the pain of not making a call to a single WxC number is less than the pain represented by waiting on the line for TCL for an hour. So, TCL has engineered their service to prevent complaints. Nice racket, nice barrier to entry for a new entrant.
As above they will complain to TCL if you can't make calls
3) WorldXChange doesn't appear to care (mistakenly so), they say call TCL.The problem is that the only person who is affected by the problem is your customer. No one else. That's why alternate root domains are priced so cheaply - because no one routes traffic to them. TCL's fault is devaluing your product. Show some anger! Seek blood! Revenge! :)
Sorry Jason absolutely wrong here and you should know better than that
4) The guy that does care can't do anything about it.Yep, it shows that there's a hole in the NZ process. Thats why I asked about the numbering plan people. They would seem to be the party who would be a clearing house for these sorts of routing problems? It sounds like it's a huge hole with a lot of potential for shenanigans on the part of the major telcos. I was just surprised to see the lack of ownership for an incomplete port of a customer. At the very least, the number of complaints you guys are getting should point out that this is something that needs to be looked at for the whole marketplace.
Well, actually, he can...
I agree he can, help us to help him by getting the TC customers to ring TC and tell them they can't ring his number, also asked him to supply me his details so I can go through the carrier side , this may take longer though, Also TC will not take any faults from our helpdesk people as I say again, we have no Authorisation to act on a TC customers behalf , the amount of trouble we and they could get into if TC acted on a request from us..... then there would a thread war damning us all to hell.... damned if we do damned if we don't.
We seem to be seeing a heck of a lot routing issues between carriers since NP came in.Oh, I agree, it's more than likely TCL's fault. However, it could also be that WxC is a little intolerant of TCL's mistakes... Perhaps WxC is rejecting incoming voice traffic if it arrives at the wrong gateway? Who knows? He has no way to get a fault raised with TCL to track the problem down.
I agree, make no mistake here NP is actually a very very tricky business and some carriers do it better than others, some seem to be downright terrible it, but when you know what is actually involved with data manipulation, switch loads, databases it is a very very complicated process, it works well for some people but it requires every carrier to do the Job right across all platforms, if one part fails then some people will be effected and in this case I'm picking TC have an issue
I think this shows that there is a gap in the fault resolution processes in the NZ telecommunications market. Are there any call completion SLAs?I apologise for coming across strongly. I've seen more than enough "not our problem, talk to them" finger pointing. I've even watched it played against our customers. It isn't good, and it isn't good and leaves me feeling dirty. :(
Yes there are, but these kinds of issue's probably do not show up, because it could be effecting only a small minority of customers, in this case possibly TC customers in one local area because the switch load details are missing for this customers number port.
Trusted
Trusted
You can never have enough Volvos!
Trusted
Trusted WorldxChange
Trusted
Trusted
Trusted
|
|
