enable passthrough of "Privacy: id" header in sip
Seem to be having an issue with RPID Privacy flag A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off I found a post at http://jira.freeswitchorg/browse/MODENDP-133 however it states it should be resolved any suggestions FreeSWITCH Version 1.0.head (svn-18032) Thanks
Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do? /b On Jul 21, 2010, at 5:35 PM, mike.burlingame wrote:
Seem to be having an issue with RPID Privacy flag
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
I found a post at http://jira.freeswitch.org/browse/MODENDP-133 however it states it should be resolved any suggestions
FreeSWITCH Version 1.0.head (svn-18032)
Thanks
Interesting question... I'd expect privacy tag on leg B should be the same as on leg A... On Wednesday 21 July 2010, Brian West wrote:
Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do?
/b
On Jul 21, 2010, at 5:35 PM, mike.burlingame wrote:
Seem to be having an issue with RPID Privacy flag
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
I found a post at http://jira.freeswitch.org/browse/MODENDP-133 however it states it should be resolved any suggestions
FreeSWITCH Version 1.0.head (svn-18032)
Thanks
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Depends... we aren't a proxy. :P /b On Jul 21, 2010, at 5:54 PM, Sergey Okhapkin wrote:
Interesting question... I'd expect privacy tag on leg B should be the same as on leg A...
On Wednesday 21 July 2010, Brian West wrote:
Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do?
/b
I need to be able to pass along the privacy requirement from the A-LEG to the B-LEG so down the line the privacy request of the call is maintained. On Jul 21, 2010, at 03:44 PM, Brian West <brian@freeswitch.org> wrote: Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do? /b On Jul 21, 2010, at 5:35 PM, mikeburlingame wrote:
Seem to be having an issue with RPID Privacy flag
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
I found a post at http://jira.freeswitch.org/browse/MODENDP-133 however it states it should be resolved any suggestions
FreeSWITCH Version 1.0.head (svn-18032)
Thanks
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Have you checked to see what variables you have on the A-Leg that might need to be exported to the B-Leg? /b On Jul 21, 2010, at 5:54 PM, mike.burlingame wrote:
I need to be able to pass along the privacy requirement from the A-LEG to the B-LEG so down the line the privacy request of the call is maintained.
On Jul 21, 2010, at 03:44 PM, Brian West <brian@freeswitch.org> wrote:
Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do?
/b
yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct? So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? On Jul 21, 2010, at 03:59 PM, Brian West <brian@freeswitch.org> wrote: Have you checked to see what variables you have on the A-Leg that might need to be exported to the B-Leg? /b On Jul 21, 2010, at 5:54 PM, mike.burlingame wrote:
I need to be able to pass along the privacy requirement from the A-LEG to the B-LEG so down the line the privacy request of the call is maintained.
On Jul 21, 2010, at 03:44 PM, Brian West <brian@freeswitch.org> wrote:
Well RPID is not the same thing as the Privacy header... which are you specifically wanting to do?
/b
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com>wrote:
yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct?
So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG?
Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/> -MC
Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info. A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote: On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com> wrote: yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct? So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/> -MC _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FS doesn't recognize "uri" value of privacy tag, the recognized values are "yes", "full", "name" and "number". Any other value is interpreted as "off". See sofia.c, lines around 6660. On Thursday 22 July 2010, mike.burlingame wrote:
Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info.
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote:
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com> wrote: yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct?
So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/>
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
is there a specification which defines this "uri" value? Mike On Jul 22, 2010, at 2:36 PM, Sergey Okhapkin wrote:
FS doesn't recognize "uri" value of privacy tag, the recognized values are "yes", "full", "name" and "number". Any other value is interpreted as "off". See sofia.c, lines around 6660.
On Thursday 22 July 2010, mike.burlingame wrote:
Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info.
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote:
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com> wrote: yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct?
So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/>
http://tools.ietf.org/html/draft-ietf-sip-privacy-00 5.2 Anonymity Header Field Definition blah blah blah..."If privacy is requested, it MUST be one or more of "full", "uri", "name", or "ipaddr"." On Sun, Aug 15, 2010 at 17:52, Michael Jerris <mike@jerris.com> wrote:
is there a specification which defines this "uri" value?
Mike
On Jul 22, 2010, at 2:36 PM, Sergey Okhapkin wrote:
FS doesn't recognize "uri" value of privacy tag, the recognized values are "yes", "full", "name" and "number". Any other value is interpreted as "off". See sofia.c, lines around 6660.
On Thursday 22 July 2010, mike.burlingame wrote:
Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info.
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote:
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com> wrote: yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct?
So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/>
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Shannon
Expiration 5/31/01 An actual RFC as opposed to a 10 year old now expired draft? Mike On Aug 17, 2010, at 2:25 PM, SP wrote:
http://tools.ietf.org/html/draft-ietf-sip-privacy-00
5.2 Anonymity Header Field Definition blah blah blah..."If privacy is requested, it MUST be one or more of "full", "uri", "name", or "ipaddr"."
On Sun, Aug 15, 2010 at 17:52, Michael Jerris <mike@jerris.com> wrote:
is there a specification which defines this "uri" value?
Mike
On Jul 22, 2010, at 2:36 PM, Sergey Okhapkin wrote:
FS doesn't recognize "uri" value of privacy tag, the recognized values are "yes", "full", "name" and "number". Any other value is interpreted as "off". See sofia.c, lines around 6660.
On Thursday 22 July 2010, mike.burlingame wrote:
Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info.
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote:
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <mike.burlingame@me.com> wrote: yeah the variable I need from the A-LEG is privacy=uri the B-LEG of FS by default is putting privacy=off - so I would guess the variable that needs to be exported would be the privacy= correct?
So the next question I would have is how do I export that that from the A-LEG to the B-LEG - I would have though FS would be Data in Data out so no need to change the RPID request from the original A-LEG? Is the variable simply named "privacy"? If so just use the export app before the bridge: <action application="export" data="privacy=${privacy}"/>
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Shannon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Oh you want current. :) No I got nothing. On Tuesday, August 17, 2010, Michael Jerris <mike@jerris.com> wrote:
Expiration 5/31/01 An actual RFC as opposed to a 10 year old now expired draft? Mike On Aug 17, 2010, at 2:25 PM, SP wrote: http://tools.ietf.org/html/draft-ietf-sip-privacy-00
5.2 Anonymity Header Field Definition blah blah blah..."If privacy is requested, it MUST be one or more of "full", "uri", "name", or "ipaddr"."
On Sun, Aug 15, 2010 at 17:52, Michael Jerris <mike@jerris.com> wrote: is there a specification which defines this "uri" value?
Mike
On Jul 22, 2010, at 2:36 PM, Sergey Okhapkin wrote:
FS doesn't recognize "uri" value of privacy tag, the recognized values are "yes", "full", "name" and "number". Any other value is interpreted as "off". See sofia.c, lines around 6660.
On Thursday 22 July 2010, mike.burlingame wrote: Ok so I am still kinda lost in trying to figure this one out here are the two headers that I am looking at - basically someone sends an invite to FS that ask's FS via RPID to hide the caller id info from downstream gateways so the A-LEG is the invite going to FS - FS takes the invite and spits out the B-LEG to go downstream HOWEVER FS does not copy the parameters correctly as you can see in the initial invite A-LEG requested in the RPID to be privacy=uri however on the B-LEG side FS set the RPID to privacy=off in turn telling gateways downstream to display the CID info.
A-LEG Remote-Party-ID: <sip:NUMBER@DOMAIN>;party=calling;screen=yes;privacy=uri
B-LEG Remote-Party-ID: "NAME" <sip:NUMBER@IPADDRESS>;party=calling;screen=yes;privacy=off
On Jul 22, 2010, at 09:35 AM, Michael Collins <msc@freeswitch.org> wrote:
On Wed, Jul 21, 2010 at 4:18 PM, mike.burlingame <
-- Shannon
participants (6)
-
Brian West
-
Michael Collins
-
Michael Jerris
-
mike.burlingame
-
Sergey Okhapkin
-
SP