Caller ID Blocking Issue
-
- Active Poster
- Posts: 51
- Joined: 12/12/2009
- SIP Device Name: PAP2T
- Firmware Version: 5.1.6(LS)
- ISP Name: BELL (12 Mbps)
- Computer OS: Windows 8
- Router: 2701HG-G
- Smartphone Model: i5800
- Android Version: 2.2
- Location: Hamilton, Ontario, Canada
Caller ID Blocking Issue
I noticed the other day when i tryed to use the +67 to activate CID blocking and noticed that its not actually working.. i've been testing this with my telus cell phone but im having no such luck.. anyone know how to correctly set this up using the PaP2T ATA?
Regional
Line1
User1
Regional
Line1
User1
- FONGO_kris
- Site Moderator
- Posts: 1937
- Joined: 05/06/2009
- SIP Device Name: Polycom 550 IP Phone
- Firmware Version: 4.2.0.0310
- ISP Name: Rogers Cable
- Computer OS: Ubuntu 11.10
- Router: Cisco E1200-N
- Smartphone Model: Samsung Galaxy S2
- Android Version: 4.0.3
- Location: Cambridge, Ontario, Canada
- Contact:
Re: Caller ID Blocking Issue
Well first lets start off with a dumb question that everyone will want to know: Are you using *67 or +67 as you typed above?
Kris
Logistics & International Purchasing | Fongo
Call us toll-free! 611 from your fongo phone or 1-855-836-3355
Please advise I will no longer be contributing to this forum for the time being. Please feel free to email me.
-----------------------------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy S2 [GT-I9100] / 3.0.15-I9100XXLPH / Thebyani v3.2
Logistics & International Purchasing | Fongo
Call us toll-free! 611 from your fongo phone or 1-855-836-3355
Please advise I will no longer be contributing to this forum for the time being. Please feel free to email me.
-----------------------------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy S2 [GT-I9100] / 3.0.15-I9100XXLPH / Thebyani v3.2
Re: Caller ID Blocking Issue
I have a friend who is using FPL via a PAP2T, and he can activate CID blocking by pressing *67 and turn it on by *68. So it should work without changing anything else.
-
- Active Poster
- Posts: 51
- Joined: 12/12/2009
- SIP Device Name: PAP2T
- Firmware Version: 5.1.6(LS)
- ISP Name: BELL (12 Mbps)
- Computer OS: Windows 8
- Router: 2701HG-G
- Smartphone Model: i5800
- Android Version: 2.2
- Location: Hamilton, Ontario, Canada
Re: Caller ID Blocking Issue
star of course considering a dial pad doesn't have a plus
- FONGO_kris
- Site Moderator
- Posts: 1937
- Joined: 05/06/2009
- SIP Device Name: Polycom 550 IP Phone
- Firmware Version: 4.2.0.0310
- ISP Name: Rogers Cable
- Computer OS: Ubuntu 11.10
- Router: Cisco E1200-N
- Smartphone Model: Samsung Galaxy S2
- Android Version: 4.0.3
- Location: Cambridge, Ontario, Canada
- Contact:
Re: Caller ID Blocking Issue
Okay and what happens when you dial *67, then your number?
Kris
Logistics & International Purchasing | Fongo
Call us toll-free! 611 from your fongo phone or 1-855-836-3355
Please advise I will no longer be contributing to this forum for the time being. Please feel free to email me.
-----------------------------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy S2 [GT-I9100] / 3.0.15-I9100XXLPH / Thebyani v3.2
Logistics & International Purchasing | Fongo
Call us toll-free! 611 from your fongo phone or 1-855-836-3355
Please advise I will no longer be contributing to this forum for the time being. Please feel free to email me.
-----------------------------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy S2 [GT-I9100] / 3.0.15-I9100XXLPH / Thebyani v3.2
-
- Active Poster
- Posts: 51
- Joined: 12/12/2009
- SIP Device Name: PAP2T
- Firmware Version: 5.1.6(LS)
- ISP Name: BELL (12 Mbps)
- Computer OS: Windows 8
- Router: 2701HG-G
- Smartphone Model: i5800
- Android Version: 2.2
- Location: Hamilton, Ontario, Canada
Re: Caller ID Blocking Issue
Well usually with any other service.. when you hit *67 you would hear a couple special beeps then back to the regular dial tone.. im not sure if its the same with fpl but yea it doesn't do that for me maybe i can try changing *67 to something else and see if it works
Re: Caller ID Blocking Issue
The *67 will only have an effect on the ATA, not with FPL. So, the ATA may not give you a confirmation beep of any sort, but it still might have an effect.leper1983 wrote:Well usually with any other service.. when you hit *67 you would hear a couple special beeps then back to the regular dial tone.. im not sure if its the same with fpl but yea it doesn't do that for me maybe i can try changing *67 to something else and see if it works
I know my friend did it just by pressing *67, I would have to ask him if it gave a new tone or beep of any sort. I know he didn't type it in every time he made a call, so it might be worth pressing *67 then putting the phone down without dialling a number. Then pick the phone up again and test it. I think he must have turned it on by accident because the other day he asked how to turn it off. I suggested *68 to him and that worked straight away.
edit: number in bold changed from *98 to *68
-
- Active Poster
- Posts: 51
- Joined: 12/12/2009
- SIP Device Name: PAP2T
- Firmware Version: 5.1.6(LS)
- ISP Name: BELL (12 Mbps)
- Computer OS: Windows 8
- Router: 2701HG-G
- Smartphone Model: i5800
- Android Version: 2.2
- Location: Hamilton, Ontario, Canada
Re: Caller ID Blocking Issue
Yea for me to enable it full time its supposed to be *81.. thats what its set to in the ata but it doesn't seem to work either. *98 on my system at least is to access the voice mail so that wouldn't work unfortunately.. would it be possible to have him screen shot the sections i posted above of his ata? if hes using the PaP2T that is
Re: Caller ID Blocking Issue
I set it up for him, so I can tell you it is exactly the same as in the guide posted in the config section here, apart from I changed the registration time down to 60 from 3600. I made a mistake in my last post, I put *98 instead of *68. Sorry my bad.leper1983 wrote:Yea for me to enable it full time its supposed to be *81.. thats what its set to in the ata but it doesn't seem to work either. *98 on my system at least is to access the voice mail so that wouldn't work unfortunately.. would it be possible to have him screen shot the sections i posted above of his ata? if hes using the PaP2T that is
I looked at my PAP2T and *81 says it is 'Block CID Per Call'. Did you change yours?
Mine is pretty default, so I know his will be the same, so I have
Block CID Act Code: *67
Block CID Deact Act Code: *68
Block CID Per Call Act Code: *81
Block CID Per Call Deact Code: *82
I also know he would not have changed other settings like Block CID Setting: (no) or Block CID Serv: (yes) from the defaults. (in brackets).
-
- Active Poster
- Posts: 51
- Joined: 12/12/2009
- SIP Device Name: PAP2T
- Firmware Version: 5.1.6(LS)
- ISP Name: BELL (12 Mbps)
- Computer OS: Windows 8
- Router: 2701HG-G
- Smartphone Model: i5800
- Android Version: 2.2
- Location: Hamilton, Ontario, Canada
Re: Caller ID Blocking Issue
I set it up for him, so I can tell you it is exactly the same as in the guide posted in the config section here, apart from I changed the registration time down to 60 from 3600. I made a mistake in my last post, I put *98 instead of *68. Sorry my bad.
I looked at my PAP2T and *81 says it is 'Block CID Per Call'. Did you change yours?
Mine is pretty default, so I know his will be the same, so I have
Block CID Act Code: *67
Block CID Deact Act Code: *68
Block CID Per Call Act Code: *81
Block CID Per Call Deact Code: *82
I also know he would not have changed other settings like Block CID Setting: (no) or Block CID Serv: (yes) from the defaults. (in brackets).
I actually did switch the per calls but even before i changed it i still had issues.. i'll try changing the block CID settings to no and see if that does anything