Text messages stopped suddenly on Telecom using ported 021 number

Forums › Spark New Zealand (including Skinny and BigPipe) › Text messages stopped suddenly on Telecom using ported 021 number

jainzi

5 posts

Wannabe Geek

#37037 6-Jul-2009 15:43

I ported my 021 number to Telecom (NZ) nearly 12 months ago and thsi has been working fine. Over the weekend I noticed that no texts were being sent or received so I called Telecom. After I eventually (4 calls later!) found someone who could give me any sensible help they taled me through 'crashing' then re-setting my phone, then they tried removing my number from the network and re-adding it. They said that the next step was to take the phone to a Telecom dealer to try porting my number to anothe phone.

This I did (after much persuasion and many more calls to Telecom). They moved my number to other phones and back to my phone but always the same issue. No texts to or from the pone with that 021 number.

I can always talk on the phones without a problem.

Has anyone else had this problem, or know the solution? They are still trying to fix it.

jaidevp

331 posts

Ultimate Geek

Trusted

Spark NZ

#232224 7-Jul-2009 22:27

Email me your number and fault reference number if you have one. I get someone to take a look.

jainzi

5 posts

Wannabe Geek

#234623 13-Jul-2009 11:26

Hi jaidevp, did you have any luck looking at the case No?
Since last post they have spoken to Alkatel who would only say that the number is commissioned correctly (big deal!) and they could not find a network problem. Telecom completely removed my 021 number from their network and re-added it, and I re-configured my phone (now 2nd time this has been tried). They also said that they had contacted Vodafone.
Is it the case that all 'ported' 021 number still go through Vodafone and messages get routed to Telecom? If so this is highly likely to be were the problem is. Does that sound logical/correct?

jaidevp

331 posts

Ultimate Geek

Trusted

Spark NZ

#234627 13-Jul-2009 11:41

Hi sorry about the delay appears to be somthing complex. I am looking into it, yes at a Network level it appears everything is correct. I am consulting with a porting/billing specialist to see what may have gone wrong in the porting.

jainzi

5 posts

Wannabe Geek

#235466 15-Jul-2009 08:31

Thanks for all your help. All working fine now. It would be good to find out what the problem was so others can be aware or so it does not happen again. I know some people almost live on texting!

johnr

19282 posts

Uber Geek
Inactive user

#235471 15-Jul-2009 08:53

Guessing

I would say your MSISDN was removed on the SMSC/SMSR Exception table for sending SMS

Cause you have a ported in number your MSISDN has to be added to a table as a one off for SMS and many other tables on different platforms

John

jainzi

5 posts

Wannabe Geek

#236289 16-Jul-2009 22:17

I beleive it was something like this, but why would one number be removed like that, perhaps just operator error?

jaidevp

331 posts

Ultimate Geek

Trusted

Spark NZ

#236307 16-Jul-2009 23:19

Yep that was it, there were a few others.. glitch in the matrix