On 01/19/2012 05:56 AM, effie mouzeli wrote:
When the date was Thu Jan 19 2012 12:12:04, Stefan Schmidt wrote:
Hello,
IMHO asterisk acts exactly as it should. How else do you think it should
it prevent sending out the callerid name or num when you set it to prohib?
This behaviour is new in 1.8, since in 1.6 it work differently (not forcing the "From"
header to the default asterisk caller ID). Does the RFC say that a UAS must change the
"From" header to secure privacy, even though there is a special header for privacy (or
set privacy=full in Remote-Party-ID)?
In case asterisk is not functioning as a PBX but as intermediate proxy, how do we secure
its interoperability with other systems? So the issue here is that we are unable to
change/keep the "From" header when CALLERID(num-pres)=prohib_passed_screen is
set.
Asterisk cannot act as a proxy, it is a B2BUA. If you want to make its
behavior *appear* to be a proxy, there are a number of things you can
do, but it will never just 'pass along' headers from an incoming INVITE
to an outgoing INVITE.
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: [email protected] | SIP: [email protected] | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
