In article <4B5AB4B0.5070308@noreply>, Steve <Steve@noreply> wrote:
>alexd wrote:
>> Meanwhile, at the uk.telecom.voip Job Justification Hearings, Steve chose
>> the tried and tested strategy of:
>>
>>> no, I don't wan to do globally, but just for a specific SIP phone.
>> ...
>>> i would prefer to do it on the SIP conf
>>
>> This kind of clever stuff will need to be done in extensions.conf, as
>> anything you did in sip.conf will apply to everything the given handset
>> does.
>>
>> I would start by putting the two special extensions in their own context [as
>> you only want CallerID barred on calls between these two handsets, and not
>> other extensions, right?]. See Gordon's post elsethread for more ideas.
>>
>>> and some phone features ( like the *34 etc.. ) can be in conflict with
>>> the Asterisk server.
>>
>> I should have thought that the feature codes are interpreted by the handset
>> before sending to Asterisk [or whatever it's calling to]. So if *34 is
>> special to the handset, the handset should interpret it before passing it on
>> to Asterisk. BICBW.
>>
>
>I just made the test. I have a Spa941 and I have :
>'Block CID Per Call Act Code:*81'
>
>I did it, dialed the number but is still displayed :-(
>
>Is there something to add on the Asterisk server ? or is it completely
>independent ?

It will depend entirely on your dialplan. Is this something you're doing
from scratch, or does it have (e.g.) FreePBX? (ie. trixbox, etc.)

It's it's something else, it may be that the something else is forcing the
caller ID to whatever you put in the database to define that phone. (Which
is what I do in my systems) Is the caller ID being display the ID string
you put in the phone or in the database on the PBX?

Gordon