Not allowed by SIM

**bugsbunny61** · 07-17-2012, 02:57 PM

I have the same issue with Samsung S3. My first S3, acted like this after a couple of days. It happened 5 times in 12 days. I figured out that restarting will bring back the outbound calling but didn't fix the issue. The FactoryReset (did it twice) didn't fix the problem, so my advice, don't do it! I returned the phone and got a second one - new phone, new SIM. After 3 days it happened again! I got the SIM card changed now and wait to see what will happen. Will keep you posted!
UPDATE: with the new SIM card, it took only a day and got the problem again! It looks like is not the phone and not the card! So, next step, escalate to Rogers!

**pheffron11** · 07-17-2012, 05:22 PM

Same problem here - Samsung S3, Rogers network, tried 2 different SIM cards. Others in our office are the same.

Rogers rep's first solution was to suggest I reset my phone. Didn't even cross his mind to mention that this would wipe out all my setup - thankfully I asked. He says Rogers has never encountered this error message in 30 years. He said he called Samsung and they aren't seeing any problems elsewhere.

He wanted to swap out my phone for a new one - but that will cost me hours of setting it up again, and now that I found this group, I'm sure it won't even fix the problem.

Appears that Roger could be facing an epidemic.

**Ch28** · 07-18-2012, 03:35 PM

I encountered the error last night. Gf was calling me, so I opened up the notification bar, turned on bluetooth, and connected my headset. By the time I was done, she had already hung up, so I quickly called her back and got the "Not allowed by sim" error. I kept calling her back and kept getting the stupid error. It wasn't until she called me back 10 minutes later, that I was able to talk to her.

I just tried making a call right now, without bluetooth, and I got the error again. I rebooted my phone and the call went through.

**ecid** · 07-19-2012, 06:12 AM

Just an update.

This has been escalated as a known issue and the issue is being investigated. It is definitely a firmware problem.

Do not change your SIM, do not SWAP the phone, this will only give you the same result.

A quick fix: Simply enabling Airplane mode, then disabling it should restore outbound call capability - annoying, I know, but it's a quick fix. If that doesn't work, a simple restart should correct the issue (This is not permanent mind you)

Will update when information becomes available.

**TadMorose** · 07-19-2012, 07:56 AM

Originally Posted by ecid

Just an update.

This has been escalated as a known issue and the issue is being investigated. It is definitely a firmware problem.

Do not change your SIM, do not SWAP the phone, this will only give you the same result.

A quick fix: Simply enabling Airplane mode, then disabling it should restore outbound call capability - annoying, I know, but it's a quick fix. If that doesn't work, a simple restart should correct the issue (This is not permanent mind you)

Will update when information becomes available.

Thanks for the update!

**intlbizman** · 07-22-2012, 01:24 PM

happens on telus too. should move to this thread to the phone forum or should i create the same thread in the telus forum?

**Eluder** · 07-22-2012, 01:26 PM

Are you saying you have the same issue with a Rogers version unlocked for use on Telus, or the Telus version gives you the same issue with a Telus sim?

**TLS2000** · 07-22-2012, 02:00 PM

This appears to be a common problem on the SGH-I747M, so it's more phone specific.

**intlbizman** · 07-22-2012, 03:45 PM

telus on telus
i understand this is the rogers forum but let's not assume everyone's a rogers customer...

**bill_n_opus** · 08-03-2012, 01:43 AM

Late to the party. Had this error message too. At the time I turned power on
and off and that worked. Hope they fix this soon.

**sudsbear** · 08-05-2012, 03:09 PM

Originally Posted by bill_n_opus

Late to the party. Had this error message too. At the time I turned power on
and off and that worked. Hope they fix this soon.

Hey, Alberta here. (south of edmonton.)

I dont have LTE here, but today was the first time this has happend. I have had my S3 for less then 24Hrs. Im happy to see im not the only one, but i was on the fence to renew my contract with rogers due to there signal/service in the first place. Having this happen is not making me a happy camper, and if something isnt done asap, il be returning my phone within the first 15days, and demanding that they cancle my contract.

**Tri3Dent** · 08-05-2012, 08:01 PM

sudsbear,

Rogers do have a return policy as long as it's within 15 days and less than 30 minutes. If you think the problem is not acceptable, they would be happy to accept it back. Now having said that, I have the same phone and I've only gotten this message like twice since getting the phone (the week it was launched).

Like someone have said, doing the airplane mode on/off fixes it. I don't think we will see a fix from Rogers right away at this moment but I'm sure it'll probably be fixed when we get Jelly Bean on our phones =) Haha I'm just ahead of myself here but I'm quite sure we'll get Jelly Bean sooner or later.

But the S3 is a very nice phone. I rather keep the device than switching to another brand/model that doesn't have the problem. Because frankly, I rarely get the message.

**danrubi** · 08-06-2012, 09:07 AM

Ya this is an ongoing problem - unfortunately, airplane mode is the best fix to date.

I spoke to a Rogers tech last week and "they are aware of the problem and are working with Samsung to deliver a fix". One thing that they asked is that when you DO have the issue, call the Samsung Tech Dept and tell them the specifics so that they can give your case to the support group that're trying to fix the problem.

Hopefully JB fix comes soon

**intlbizman** · 08-06-2012, 01:14 PM

Originally Posted by danrubi

Ya this is an ongoing problem - unfortunately, airplane mode is the best fix to date.

I spoke to a Rogers tech last week and "they are aware of the problem and are working with Samsung to deliver a fix". One thing that they asked is that when you DO have the issue, call the Samsung Tech Dept and tell them the specifics so that they can give your case to the support group that're trying to fix the problem.

Hopefully JB fix comes soon

contact info?

**acidsnow** · 08-08-2012, 10:43 AM

I got rogers with the new 6gb lte plan too, and I'm having the same problem also.

I called rogers long story short, they got me to do a factory reset 7 times - what a joke these guys are, I think they believe its funny or a good way to show the customer they have no idea what they are doing. They replaced the phone twice (after having to fight them them to because they wanted to send it in for repair even though the phone was 1 day old with only 5 min talk time) They also replaced the SIM 2 times.

They did a "network reset" on their end, still no success. Finally 2nd level Rogers support said we give up "we don't know - call Samsung."

I called Samsung, first guy said hes never heard of the problem. After being placed on hold for quite a while he came back and said that they are aware that Rogers and Galaxy S3 do not work and have this problem. He said Samsung and Rogers are working togather to see if they can fix the problem. His said we have no choice but to wait for a "possiblity" of a fix. -but no gaurantee.

I told Samsung thats not very fair, and he said Rogers is the only service provider with this problem. Great, F'd by Rogers again, you think I'd learn my lesson.

Anyway hes said next time DO NOT BUY ROGERS, he said buy Bell and they don't have this problem.