Hello,
it's been a while since my last visit. I thought I had everything running smoothly, but now I discovered I can't hide my CID.
My telco requires the *67# code to mask it once but if I receive a dial error if I use it.
I tried altering Code 5 in the star codes section, and if I change it to "*67#, Block Caller ID Once, set($Bci1,1)" the number is correctly dialed, but CID is in the clear.
I suspect I also have to change something in the dialplan to differentiate between landline and voip, but I wouldn't know where to start. ???
Any help will be greatly appreciated.
Regards
aloysius,
The OBi reserves the "*" as a special character. Ianobi has come up with a way to overcome this. He should be along shortly to explain how.
aloysius,
Let me see if I understand the question :-\
*67 blocks caller ID one time when dialling from the OBi110 using voip.
You wish to send *67# to your telco PSTN line to stop the telco sending out your Caller ID.
If I understand correctly, then there are several possible answers.
Leave the OBi *67 as it is. When dialling via your telco PSTN line start with #, which bridges the phone port to the line port, then dial out using *67# followed by the number.
Another answer is to change the number in OBi Star Code 5 position to different digits, maybe *66, and use that for voip calls. Then add *67#xx. to the beginning of your Line Port DigitMap , so
(xxxxxxxS4|1xxxxxxxxxx|xx.)
Change to:
(*67#xx.|xxxxxxxS4|1xxxxxxxxxx|xx.)
Now, assuming that Phone Port PrimaryLine is PSTN, then any call starting *67# will go to the telco. The DigitMap can be refined if the calls starting with *67# are of a definite number of digits.
I hope I got the question right!!
ianobi,
I thought that you where going to show the @@ thingy that you figured out.
Zappy,
That was more to do with calls via OBiTALK trunks. I don't think it applies here. Although, I'm still not sure if I am answering the right question here :)
ianobi,
I believe it is possible to insert * as a literal string by surrounding it in a quote ". It then could be possible to control the * to mean something other what the OBi expects to see in the star code list.
QBZappy,
yes, I see what you mean. The problem here (I think) is dialling *67# to go out on PSTN, which I guess is the Primary Line. *67 might get swallowed by the OBi and used as the Star Code and never get to line. The # could also be a problem as OBi sees that just as an instruction to send preceding digits out to line.
My first idea was the most simple - press # get telco dial tone then dial *67# etc each time you want to hide your Caller ID.
The other idea probably needs refining. Stop *67 from being a Star Code (maybe change to *66). Then add *67<#>xx. to the Line Port DigitMap. Then only dial *67 on call going out to PSTN and let OBi insert the #
I'm really not sure now if I am "on topic" or "off topic" :)
Quote from: ianobi on September 29, 2012, 09:05:10 AM
aloysius,
Let me see if I understand the question :-\
*67 blocks caller ID one time when dialling from the OBi110 using voip.
You wish to send *67# to your telco PSTN line to stop the telco sending out your Caller ID.
If I understand correctly, then there are several possible answers.
Leave the OBi *67 as it is. When dialling via your telco PSTN line start with #, which bridges the phone port to the line port, then dial out using *67# followed by the number.
Another answer is to change the number in OBi Star Code 5 position to different digits, maybe *66, and use that for voip calls. Then add *67#xx. to the beginning of your Line Port DigitMap , so
(xxxxxxxS4|1xxxxxxxxxx|xx.)
Change to:
(*67#xx.|xxxxxxxS4|1xxxxxxxxxx|xx.)
Now, assuming that Phone Port PrimaryLine is PSTN, then any call starting *67# will go to the telco. The DigitMap can be refined if the calls starting with *67# are of a definite number of digits.
I hope I got the question right!!
First of all, thanks for the reply. Unfortunately the notification for this thread wasn't set, so I read it only now.
I just tested the solution and it works perfectly!
I wish I could wrap my head around all these parameters; for some reason I can't seem to
get it.
So, once again, many thanks for your help.
P.S: do you think there's a way to combine the (now) *66 command with **1 ?
It is possible to make Star Codes Trunk specific.
The default in Star Code slot 5 was:
*67, Block Caller ID Once, set($BCI1,1)
- Enable masking of caller ID information once for the next call on any trunk.
You changed it to *66. If you further add in SP1 as shown here:
*66, Block Caller ID Once, set(SP1($BCI1,1))
- Enable masking of caller ID information once for the next call on SP1 trunk.
I have not tried this! Also, it means that *66 would only be able to be applied to sp1 and no other trunk.
I suggested *66 as it seems to be spare in my Obi110. However, I note in the ObiDeviceAdminGuide it now seems to be in use for:
Code19 Default = Repeat Dial Star Code *66, Repeat Dial, rpdi($Ldn)
I'm running the latest firmware for the Obi110 and it still has *66 spare.
Quote from: ianobi on November 01, 2012, 09:45:42 AM
It is possible to make Star Codes Trunk specific.
The default in Star Code slot 5 was:
*67, Block Caller ID Once, set($BCI1,1)
- Enable masking of caller ID information once for the next call on any trunk.
You changed it to *66. If you further add in SP1 as shown here:
*66, Block Caller ID Once, set(SP1($BCI1,1))
- Enable masking of caller ID information once for the next call on SP1 trunk.
I have not tried this! Also, it means that *66 would only be able to be applied to sp1 and no other trunk.
I suggested *66 as it seems to be spare in my Obi110. However, I note in the ObiDeviceAdminGuide it now seems to be in use for:
Code19 Default = Repeat Dial Star Code *66, Repeat Dial, rpdi($Ldn)
I'm running the latest firmware for the Obi110 and it still has *66 spare.
Unfortunately it didn't work :-\ I hear an immediate congestion tone.
*66 appears to be free on my OBi110 (Code19= *05, Repeat Dial, rpdi($Ldn)), but also I'm still running 1.3.0: do you think upgrading would change anything about this?
I should have said SoftwareVersion 1.3.0 (Build: 2744), which is the latest and *66 is still spare.
How about trying the default setting with *66:
*66, Block Caller ID Once, set($BCI1,1)
Then dial **1 followed by the number.
Quote from: ianobi on November 01, 2012, 10:28:23 AM
I should have said SoftwareVersion 1.3.0 (Build: 2744), which is the latest and *66 is still spare.
How about trying the default setting with *66:
*66, Block Caller ID Once, set($BCI1,1)
Then dial **1 followed by the number.
1.3.0 (Build: 2690) for me.
With that setting, **1 works but the number is in the clear.
*66<number> doesn't appear to have any effect, it dials with the default port (LINE) and CID is still present.
Just to be clear:
You dial *66, which gives you dial tone. Then you dial **1 followed by the number.
The call should have gone out on sp1 with or without Caller ID.
Quote from: ianobi on November 01, 2012, 10:59:30 AM
Just to be clear:
You dial *66, which gives you dial tone. Then you dial **1 followed by the number.
The call should have gone out on sp1 with or without Caller ID.
Sorry, I understand now.
The procedure works, but the CID is still present. :-\
That's odd. I'm running out of ideas ??? Also running out of time for today. Over the next few days I will try to reproduce exactly what you are doing on my OBi and see if I can figure something out.
Keep experimenting, I find trial and error is a good method :)
Quote from: ianobi on November 01, 2012, 11:18:15 AM
That's odd. I'm running out of ideas ??? Also running out of time for today. Over the next few days I will try to reproduce exactly what you are doing on my OBi and see if I can figure something out.
Keep experimenting, I find trial and error is a good method :)
I will, thanks for your help.
First the corrections From the ObiDeviceAdminGuide:
$BCI = block outbound caller-ID enable (trunk specific; admissible value: 0 for disable, 1 for enable)
$BCI1 = block caller-ID once (global; admissible value: 1 for enable)
So the persistant version of blocking can be trunk specific, but the "block once" has to be global – all trunks.
From my experiments, all that is happening here is that if you use *67 (*66 in your case), then all that happens is that Obi blocks Caller ID Name.
I tried using "Caller ID Spoofing" (not using Star Codes). This can be made to work, but then most providers use the Caller ID as part of the call authentication process, so the call fails. I was using sip2sip for my experiments – calls fail without Caller ID.
Is this another case of sending a code to your service provider to get them to block your Caller ID from going forward to the called number?
Quote from: ianobi on November 02, 2012, 04:08:50 AM
First the corrections From the ObiDeviceAdminGuide:
$BCI = block outbound caller-ID enable (trunk specific; admissible value: 0 for disable, 1 for enable)
$BCI1 = block caller-ID once (global; admissible value: 1 for enable)
So the persistant version of blocking can be trunk specific, but the "block once" has to be global – all trunks.
From my experiments, all that is happening here is that if you use *67 (*66 in your case), then all that happens is that Obi blocks Caller ID Name.
I tried using "Caller ID Spoofing" (not using Star Codes). This can be made to work, but then most providers use the Caller ID as part of the call authentication process, so the call fails. I was using sip2sip for my experiments – calls fail without Caller ID.
Is this another case of sending a code to your service provider to get them to block your Caller ID from going forward to the called number?
Unfortunately most of what you said is Greek to me. :D
I saw an X_SpoofCallerID parameter under ITSP Profile A, but there's only a checkbox as value. I understand that's only to allow it, but where is the outgoing CID supposed to be specified? ???
Anyway this issue is not really important for me: the real crux was with *67# and that has been solved.
x_calleridspoofing is only for bridged calls. You don't provide the information, it is taken from the original call that id being bridged.
X_CallerIdSpoofing
Allow outbound Caller ID spoofing. If set to Yes, device will attempt to set the caller-id name and userid field in the FROM header to that of a remote caller in the case of a bridged call (from another trunk, such as PSTN Line or another SP Service).
Otherwise, device always its own account information to form the FROM header.
Note that most service provider will not allow originating a call if the FROM header field does not match the account credentials. Enable this option only if you are sure that the service provider allows it, e.g. an IP PBX may allow it.
@ jimates:
Everything you say is true. However, in additon it is possible to "invent" Caller ID by setting Allow Outbound Caller ID Spoofing to Yes and putting a rule such as this:
{(<**2:>(Msp2)):sp2(123456>)}
into the Phone Port OutboundCallRoute. This will change Caller ID for calls dialled with **2 to 123456.
Anyhow, it's all a bit academic as the result with most service provider is that the call fails its authentication process.
Another little trip down a wandering tangent of a lane :)
Quote from: jimates on November 02, 2012, 05:48:59 AM
x_calleridspoofing is only for bridged calls. You don't provide the information, it is taken from the original call that id being bridged.
X_CallerIdSpoofing
Allow outbound Caller ID spoofing. If set to Yes, device will attempt to set the caller-id name and userid field in the FROM header to that of a remote caller in the case of a bridged call (from another trunk, such as PSTN Line or another SP Service).
Otherwise, device always its own account information to form the FROM header.
That may explain why VoIP.ms is showing my account number instead of my callerID for outbound calls. I swear at one time it did work right for outbound.
Ostracus,
If you want to spoof with voipms, both name and number can be spoofed. You need to set it up in two different places. The number can be spoofed on the voipms portal, and the name can be spoofed with whatever name you set up in the sip client (OBi/softphone). I use it occasionally when I want to coerce someone to answer the phone, who would otherwise prefer not to speak with me. ;)
I think my question is related to this discussion... but it is a simple one.
We have a Telus voicemail subscription, to listen to voicemails we need to dial *98
So... how do I convince Obi110 to dial that and not go into some internal thingie? :-[
Quote from: ianobi on September 29, 2012, 09:05:10 AM
... When dialling via your telco PSTN line start with #, which bridges the phone port to the line port, then dial out using *67# followed by the number.
Wait wait... would that do the trick? Just dial
#*98 ?
Edit: ok I get it now... you need to press # then call that, after that *98.
Our system is set up that a long press on the 1 dials the voicemail.
Can I change it so that it will ring # - Dial - *98?
1st: Make sure *98 is not listed in the star codes list. If it is, simply delete it. [It is on line 28 in my 110]
2nd: Add *98 to the phone port digit map
3rd [a little more tricky] you have to make sure *98 is in the Line port Digit Map. If the PSTN line is set to be your primary line it is as simple as adding *98 to the Line port Digit Map. I have two codes that I use with my VOIP service provider that way.
*edited* I was assuming Telus was a PSTN [landline] company. If that isn't the case, simply add the *98 to which ever Service Provider -> ITSP[A or B] -> General -> digit map is correct.
Sorry for the delayed response, THANKS for your kind reply! :-*
Yes, Telus is a Canadian landline company :)
Edit: Ok I am such an noobie :) This is my Phone digit map
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
And this the Line port digit map:
([2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)
So... how do I add this *98 to those two lines? I already deleted the star code ;D
The Phone Port DigitMap can be ignored in this slightly odd instance. The OBi is "hard-wired" to accept *xx for its own Star Codes.
You may wish to use other Telus Star Codes as well *98, so long as they do not conflict with the OBi Star Codes. You should be ok just making this change to your Line Port DigitMap:
(*xx|[2-9]11S0|<250>[2-9]xxxxxx|250xxxxxxx|180xxxxxxxx|188xxxxxxxx|<**1>1[2-79]xxxxxxxxx|<**1>011xx.)
The *xx will allow any two digit star codes to pass through to Telus, so long as they are not OBi Star Codes.
The Obi is "Hard wired" to accept them but only if they are in the star code list. I use *7[89] with Callcentric and have deleted those two codes from the star code list. If I remove *7[89] from the phone port digit map I get error tone when it is dialed. So it looks to me like *98 or (*xx, whichever you choose) will need to be added to the phone port digit map the same as the Line port Digit Map.
ProfTech,
Interesting! I did check to make sure. With *xx in the Line Port DigitMap and no change to Phone Port DigitMap, I could dial any *xx number that was not an OBi Star Code. I wonder if the format *7[89] makes a difference.
Maybe Sophia would be kind enough to only put the *xx in the Line Port DigitMap, then try to see if it works. If not then *xx can be added to the Phone Port DigitMap.
These OBi devices keep throwing up little oddities ::)
Edit: Through all this, I am assuming that the Primary Line is PSTN.
My mistake. I'll bet you're probably correct in figuring the *7[89] is throwing a wrinkle into it.
Yet another undocumented OBi fact!
Quote from: ianobi on November 12, 2012, 10:35:11 AM
Maybe Sophia would be kind enough to only put the *xx in the Line Port DigitMap, then try to see if it works. If not then *xx can be added to the Phone Port DigitMap.
These OBi devices keep throwing up little oddities ::)
Edit: Through all this, I am assuming that the Primary Line is PSTN.
You're the best!!! :-* It works puhfectly ;D Thanks!
Yes I set up the Primary Line as PSTN :)
I think we're all set now... until I want to monkey with it again just because
I like to drive hubby crazy I like toys :P
I have one more question about star codes... I just found out that Freephoneline uses the same star code to access their voicemail as Telus uses - both *98
So how can I reach FPL? When I just call *98 I'm getting to Telus... but when I call **2 and then *98 I seem to go to Telus as well ???
If you only need *98 for Telus, I recommend you use *98 in the Line Port Digit map instead of *xx. Then you can simply pick another two digit star code that isn't in use and use that code for FPL. Example: *94 isn't used. Line 30 is empty in my 110. You should be able to "Build your own" star code on line 30. I think you could do this in two steps. First, pick a speed dial slot that is empty. I used slot 21. Insert sp2(*98) on line 21. Next, insert *94, Voice Mail, call($spd[21]) on star code line 30. Then any time you press *94, the Obi should send *98 out to sp2 [FPL]. The only snag in all this is if you are using the portal to do your config I am not sure it will let you enter "sp2(*98)" for a speed dial. If you are doing everything directly on the Obi you can enter it with no problem. Be advised you can't use both methods of configuration. Obitalk will over write anything entered directly on the Obi.
Thanks Prof, I almost got you ;D
Just to verify that I understand you correctly, do you suggest the following?
- Go to Star Code Profile B
- untick line 21
- replace whats there - *74([1-9]|[1-9]x), Set Speed Dial, coll($Spd[$Code]) - with sp2(*98)
- untick line 30
- add *99, Voice Mail, call($spd[21]) in that line (I chose 99 which is also unused)
I don't think I'm using the portal, I chose the router address 192.168 etc...
Oh and I don't really need a speed dial, if I can just dial **99... Don't mind dialing *98 either :)
Thanks! :-*
I thought maybe my first post was a little confusing. Try this:
1. Go to Physical Interfaces -> Phone port -> Calling Features -> Star Code Profile and check to see which star code profile you are using. You don't need to change it, just check to see which one is in use. It should be A unless you changed it.
2. Go to Star Codes -> Star Code Profile A [or B, which ever is correct]. Find an empty line and insert *99, Voice Mail, call($spd[21])
3. Go to User Settings -> Speed Dials -> Line 21 [I'm assuming it is empty] and insert sp2(*98)
That's it! I am assuming you have FPL on sp2. If FPL is on sp1 just use sp1(*98) instead. The beauty of doing it this way is you don't need to mess with any digit maps, however as I said before be sure and change the *xx you put in the Line port digit Map to *98 or else the Obi will "steal" your key presses when you press *99 and it won't work.
Perfect! That did the trick ;D All set now ;D