Hi, how can I setup a pure outbound proxy that the IP address of the SIP INVITE is the outbound proxy but SIP-TO is the address of the PBX (and not the outbound proxy address) In my understanding the outbound proxy should only change the IP destination address and nothing in the original SIP packet. Best Regards, Bernhard
Hi Berhnard, If I've understood the question - you want to send the INVITE to a specified IP address - then you can do this in the dialplan: <action application="set" data="sip_h_Route=<sip:@1.2.3.4;lr>" /> <action application="bridge" data="sofia/gateway/name/01231231234@whatever.it.is"/> Cheers -- Dave
Hi,
how can I setup a pure outbound proxy that the IP address of the SIP INVITE is the outbound proxy but SIP-TO is the address of the PBX (and not the outbound proxy address)
In my understanding the outbound proxy should only change the IP destination address and nothing in the original SIP packet.
Best Regards, Bernhard
_______________________________________________ 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
-- David Knell, Director, 3C Limited T: 020 8114 8901 F: 020 3002 7257 M: 001 415 630 3031 http://www.3c.co.uk
Thx, I will try that! Regards, Bernhard Am Freitag, den 20.06.2008, 13:51 +0100 schrieb David Knell:
Hi Berhnard,
If I've understood the question - you want to send the INVITE to a specified IP address - then you can do this in the dialplan: <action application="set" data="sip_h_Route=<sip:@1.2.3.4;lr>" /> <action application="bridge" data="sofia/gateway/name/01231231234@whatever.it.is"/>
Cheers --
Dave
Hi,
how can I setup a pure outbound proxy that the IP address of the SIP INVITE is the outbound proxy but SIP-TO is the address of the PBX (and not the outbound proxy address)
In my understanding the outbound proxy should only change the IP destination address and nothing in the original SIP packet.
Best Regards, Bernhard
_______________________________________________ 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
Hi all! I have (may be) stupid question: How to hide caller identity in Freeswitch, i.e. provide CLIR? I try following (I found it somewhere in the wiki): <action application='set' data='Caller-Privacy-Hide-Number=yes'/> <action application='set' data='Callee-Privacy-Hide-Name=yes'/> <action application='privacy' data='xxx'/> where xxx I replace with all mentioned values - no|yes|name|full|number I try all combinations of above methods, but "From:" header still contains name and number setted-up in Directory and Remote-Party-ID is also included with caller datas and , btw, there is no Privacy header... What I'm missing? Any hints are really welcome :-) Best regards, kokoska.rokoska
What does the remote-party-id header say? /b On Jun 20, 2008, at 8:39 AM, kokoska rokoska wrote:
Hi all!
I have (may be) stupid question: How to hide caller identity in Freeswitch, i.e. provide CLIR?
I try following (I found it somewhere in the wiki):
<action application='set' data='Caller-Privacy-Hide-Number=yes'/> <action application='set' data='Callee-Privacy-Hide-Name=yes'/> <action application='privacy' data='xxx'/> where xxx I replace with all mentioned values - no|yes|name|full| number
I try all combinations of above methods, but "From:" header still contains name and number setted-up in Directory and Remote-Party-ID is also included with caller datas and , btw, there is no Privacy header...
What I'm missing? Any hints are really welcome :-)
Best regards,
kokoska.rokoska
_______________________________________________ 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
Brian West sip:brian@freeswitch.org
It is based on what I put as data into "privacy" directive: <action application='privacy' data='full'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=full <action application='privacy' data='number'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=number ... And, like I wrote before, "From:" header is unttached, thus always contains: From: "name" <sip:number@ip>;tag=Ky5yFavK7gUNB Best regards, kokoska.rokoska Brian West napsal(a):
What does the remote-party-id header say?
/b
On Jun 20, 2008, at 8:39 AM, kokoska rokoska wrote:
Hi all!
I have (may be) stupid question: How to hide caller identity in Freeswitch, i.e. provide CLIR?
I try following (I found it somewhere in the wiki):
<action application='set' data='Caller-Privacy-Hide-Number=yes'/> <action application='set' data='Callee-Privacy-Hide-Name=yes'/> <action application='privacy' data='xxx'/> where xxx I replace with all mentioned values - no|yes|name|full| number
I try all combinations of above methods, but "From:" header still contains name and number setted-up in Directory and Remote-Party-ID is also included with caller datas and , btw, there is no Privacy header...
What I'm missing? Any hints are really welcome :-)
Best regards,
kokoska.rokoska
_______________________________________________ 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
Brian West sip:brian@freeswitch.org
_______________________________________________ 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
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch". /b On Jun 20, 2008, at 11:36 AM, kokoska rokoska wrote:
It is based on what I put as data into "privacy" directive:
<action application='privacy' data='full'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=full
<action application='privacy' data='number'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=number
...
And, like I wrote before, "From:" header is unttached, thus always contains: From: "name" <sip:number@ip>;tag=Ky5yFavK7gUNB
Best regards,
kokoska.rokoska
Brian West napsal(a):
What does the remote-party-id header say?
/b
On Jun 20, 2008, at 8:39 AM, kokoska rokoska wrote:
Hi all!
I have (may be) stupid question: How to hide caller identity in Freeswitch, i.e. provide CLIR?
I try following (I found it somewhere in the wiki):
<action application='set' data='Caller-Privacy-Hide-Number=yes'/> <action application='set' data='Callee-Privacy-Hide-Name=yes'/> <action application='privacy' data='xxx'/> where xxx I replace with all mentioned values - no|yes|name|full| number
I try all combinations of above methods, but "From:" header still contains name and number setted-up in Directory and Remote-Party- ID is also included with caller datas and , btw, there is no Privacy header...
What I'm missing? Any hints are really welcome :-)
Best regards,
kokoska.rokoska
_______________________________________________ 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
Brian West sip:brian@freeswitch.org
_______________________________________________ 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
_______________________________________________ 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
If you want to actually not send to them you need to set the effective caller id name/number. Mike On Jun 20, 2008, at 1:10 PM, Brian West wrote:
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch".
/b
On Jun 20, 2008, at 11:36 AM, kokoska rokoska wrote:
It is based on what I put as data into "privacy" directive:
<action application='privacy' data='full'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=full
<action application='privacy' data='number'/> => Remote-Party-ID: "name" <sip:number@ip>;screen=yes;privacy=number
...
And, like I wrote before, "From:" header is unttached, thus always contains: From: "name" <sip:number@ip>;tag=Ky5yFavK7gUNB
Best regards,
kokoska.rokoska
Brian West napsal(a):
What does the remote-party-id header say?
/b
On Jun 20, 2008, at 8:39 AM, kokoska rokoska wrote:
Hi all!
I have (may be) stupid question: How to hide caller identity in Freeswitch, i.e. provide CLIR?
I try following (I found it somewhere in the wiki):
<action application='set' data='Caller-Privacy-Hide-Number=yes'/> <action application='set' data='Callee-Privacy-Hide-Name=yes'/> <action application='privacy' data='xxx'/> where xxx I replace with all mentioned values - no|yes|name|full| number
I try all combinations of above methods, but "From:" header still contains name and number setted-up in Directory and Remote-Party- ID is also included with caller datas and , btw, there is no Privacy header...
What I'm missing? Any hints are really welcome :-)
Best regards,
kokoska.rokoska
_______________________________________________ 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
Brian West sip:brian@freeswitch.org
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ 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
That is true... the remote carrier might or might not honor the flags. Love this stuff eh? /b On Jun 20, 2008, at 12:24 PM, Michael Jerris wrote:
If you want to actually not send to them you need to set the effective caller id name/number.
Mike
On Jun 20, 2008, at 1:10 PM, Brian West wrote:
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch".
/b
Many tanks Mike & Brian for your help! I know I could explicitly set the effective caller id, but I hope there is other and a little bit comfortable way :-) Mainly because I have to record valid CLIP in CDR (and show it if somebody interested - like police etc.) and this force me to use another variables to store CLIP... And even thou, I realy have to erase RPID header, or rewrite it to "anonymous@invalid" :-) Now about carriers: I know I should always send valid CLIP on (SIP|SS7) interconnection and CLIP will erase terminating operator if CLIR is requested (this scenario is forced by law in most EU countries). And - in simmilar way - I have to erase CLIP if I am the terminating switch and my subscriber or interconnected operator requests CLIR. The question isn't "What and when I should do/send?" :-) I'm very sure in it for years... Whats going on is "How to do it with FreeSWITCH?" :-) So my last question about CLIP etc.: Is there a way (other than modifying sources) how to remove RPID? Thanks once more, Brian and Mike, best regards, kokoska.rokoska Brian West napsal(a):
That is true... the remote carrier might or might not honor the flags. Love this stuff eh?
/b
On Jun 20, 2008, at 12:24 PM, Michael Jerris wrote:
If you want to actually not send to them you need to set the effective caller id name/number.
Mike
On Jun 20, 2008, at 1:10 PM, Brian West wrote:
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch".
/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
Brian West wrote:
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch".
That's not quite the case. In the good old world, there was generally a fairly clear distinction between users and carriers. Caller ID would be passed between carriers with the privacy flags set or not as required, but, if it had been withheld by a caller, would not then be delivered to the end user. Otherwise you're essentially giving it to the end user and asking them not to peek, which isn't terribly secure. Nowadays, if I want to withhold my CLI, I don't send anything. That works pretty well. Don't put junk in - I know that I can't call various destinations over BT if I use something bogus (like na, or thiscliisaloadofoldbollocks[1]); I get a 403 Forbidden back. --Dave [1] "bollocks" was once defined on Wikipedia as "the Swiss army knife of andrological profanities" - unfortunately, like most excellent stuff on the word's most comprehensive Star Trek factsheet encyclopedia anyone can ruin, that particular gem's been edited out. http://en.wikipedia.org/wiki/Bollocks is still worth a read, though.
David Knell napsal(a):
Brian West wrote:
It will always contain the number. Its the far ends responsibility to honor the privacy flags. The same happens on a PRI as far as I have seen. Nobody should have the ability to withhold that info from your "switch".
That's not quite the case. In the good old world, there was generally a fairly clear distinction between users and carriers. Caller ID would be passed between carriers with the privacy flags set or not as required, but, if it had been withheld by a caller, would not then be delivered to the end user.
Yes, I 100% agree! And in SIP world (at least around me :-) it works the same way - me and other TSP sends valid CLIP in between (Telecommunication Office supervise it very heavy) and if Privacy flag is set we don't deliver CLIP to end user, only store it for (possible) later processing...
Otherwise you're essentially giving it to the end user and asking them not to peek, which isn't terribly secure.
:-)
Nowadays, if I want to withhold my CLI, I don't send anything. That works pretty well. Don't put junk in - I know that I can't call various destinations over BT if I use something bogus (like na, or thiscliisaloadofoldbollocks[1]); I get a 403 Forbidden back.
Thats very strange for me :-) All TSPs around - if you are "only" end user - force you to send valid CLIP (From: header) or silently rewrite it. Some bigger customers (corporations etc.) have "the privilege" to send whatever CLIP they want because they are directly responsible for CLIP validity to local Telecommunication Office... Best regards, kokoska.rokoska
kokoska rokoska wrote:
David Knell napsal(a):
Nowadays, if I want to withhold my CLI, I don't send anything. That works pretty well. Don't put junk in - I know that I can't call various destinations over BT if I use something bogus (like na, or thiscliisaloadofoldbollocks[1]); I get a 403 Forbidden back.
Thats very strange for me :-) All TSPs around - if you are "only" end user - force you to send valid CLIP (From: header) or silently rewrite it. Some bigger customers (corporations etc.) have "the privilege" to send whatever CLIP they want because they are directly responsible for CLIP validity to local Telecommunication Office...
Sorry - what I didn't make clear is that we are connected as a "carrier" - we treat our end users in exactly the way you suggest. Cheers -- Dave -- David Knell, Director, 3C Limited T: 020 8114 8901 F: 020 3002 7257 M: 001 415 630 3031 http://www.3c.co.uk
David Knell napsal(a):
kokoska rokoska wrote:
David Knell napsal(a):
Nowadays, if I want to withhold my CLI, I don't send anything. That works pretty well. Don't put junk in - I know that I can't call various destinations over BT if I use something bogus (like na, or thiscliisaloadofoldbollocks[1]); I get a 403 Forbidden back.
Thats very strange for me :-) All TSPs around - if you are "only" end user - force you to send valid CLIP (From: header) or silently rewrite it. Some bigger customers (corporations etc.) have "the privilege" to send whatever CLIP they want because they are directly responsible for CLIP validity to local Telecommunication Office...
Sorry - what I didn't make clear is that we are connected as a "carrier" - we treat our end users in exactly the way you suggest.
Cheers --
Dave
Many thanks Dave for clarification! :-) So you are in the same position as I am - could I ask you how do you handle CLIR? On local calls and received calls from other carriers too. Outgoing calls is simple - I could just append "Privacy: id" header :-) Thanks a lot, best regards, kokoska.rokoska
participants (5)
-
Bernhard Suttner
-
Brian West
-
David Knell
-
kokoska rokoska
-
Michael Jerris