VoIP Mailing List Archives

[kawarod at laposte.net]

Dear list,

I'd like to rewrite the number in the Remote Party ID header and only in
this header.

ex: I'd like to prefix the caller ID with a prefix code (000 in this
example) in the RPID header :

From: Anonymous<sip:anonymous@anonymous.invalid>;tag=1208367
Remote-Party-ID:
<sip:123456@10.10.10.10:5062;user=phone>;privacy=full;screen=yes;party=calling

should become:
From: Anonymous<sip:anonymous@anonymous.invalid>;tag=1208367
Remote-Party-ID:
<sip:000123456@10.10.10.10:5062;user=phone>;privacy=full;screen=yes;party=calling

But the From field should remain unchanged.

And how to strip this prefix:
From: Anonymous<sip:anonymous@anonymous.invalid>;tag=1208367
Remote-Party-ID:
<sip:000123456@10.10.10.10:5062;user=phone>;privacy=full;screen=yes;party=calling

should become:
From: Anonymous<sip:anonymous@anonymous.invalid>;tag=1208367
Remote-Party-ID:
<sip:123456@10.10.10.10:5062;user=phone>;privacy=full;screen=yes;party=calling


regards.

_______________________________________________
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 at freeswitch.org]

Well this depends on how you're placing the call.. if its a standard bridge you can on the A-Leg set "effective_caller_id_number=000${caller_id_number}" before you call bridge.

Is the from already in the correct format?


/b

On Mar 5, 2009, at 6:12 AM, rod wrote:

[kawarod at laposte.net]

Hi Brian,

if I use the function effective_caller_id_number with my INVITE, I get this:

From: "Anonymous" <sip:000000anonymous@172.29.0.5>;tag=17geyFjX5p0gS.

this is not exactly what I'm looking for :p

rod


Brian West wrote:

[kawarod at laposte.net]

the A leg invite looks like this:
From: "Anonymous"<sip:anonymous@anonymous.invalid;user=phone>

it has been rewritten like this:
From: "Anonymous" <sip:000000anonymous@172.29.0.5>

rod

rod wrote:

[dujinfang at gmail.com]

try
bridge
({effective_caller_id_name
="your_name",effective_caller_id_number="0000"}sofia/b-leg)

On Mar 5, 2009, at 9:00 PM, rod wrote:

[kawarod at laposte.net]

using these functions like this did nothing on the SIP INVITE packet :'(

seven wrote:

[dujinfang at gmail.com]

How about this?

bridge
({origination_caller_id_name
="your_name",origination_caller_id_number="0000"}sofia/b-leg)


On Mar 6, 2009, at 3:51 PM, rod wrote:

[dave at 3c.co.uk]

Hi Rod,

You can set it directly:
<action application="set"><![CDATA[sip_h_Remote-Party-Identity="${caller_id_number}" [url=sip:{$caller_id_number}@1.2.3.4]<sip:{$caller_id_number}@1.2.3.4>[/url];screen=yes;privacy=off]]></action>
<action application="bridge" data="sofia/gateway/wherever/+$1"/>

--Dave

[kawarod at laposte.net]

Hi David,

already tried this :p
the pbm is that this doesn' modify the RPID header, but it adds a new
one so that I have 2 RPID header in the SIP INVITE

rod

David Knell wrote:

[kawarod at laposte.net]

Hi all,

it seems there is no way to do this

It could be great to be able to:
- decide if RPID should be present or not in the B leg for an
outbound call
- make RPID header fully customizable with variables
- filter RPID for inbound call

I saw that kokoska rokoska created a jira bounty for 50$: Make RPID SIP
header optional

I'll add 150$ for this if I could manage RPID as described above.
Sorry to use mailing list for this, I'm unable to add a note on jira for
this bounty.

regards,
rod

rod wrote:

[kokoska.rokoska at pos...]

rod napsal(a):

[kawarod at laposte.net]

Yes I know, it's deprecated but many peers still rely on this and
P-Asserted-ID is not widely spread (my own experience).
moreover if we could strip the RPID, we could write a new one, but It
could be very convenient to get access to the fields in this header for
manipulation.

thanks for supporting this request :p

kokoska rokoska wrote:

[kokoska.rokoska at pos...]

rod napsal(a):

[anthony.minessale at g...]

Latest SVN:

Send no extra caller id info:
{sip_cid_type=none}sofia/default/user@example.com (user@example.com)

Send RPID (default)
{sip_cid_type=rpid}sofia/default/user@example.com (user@example.com)

Send P-XXX-Identity
{sip_cid_type=pid}sofia/default/user@example.com (user@example.com)

Send RPID with chosen content
{sip_cid_type=rpid,origination_caller_id_name=test,origination_caller_id_number=1234}sofia/default/user@example.com (user@example.com)

[ Show » ]
user@example.com (user@example.com) Send RPID (default) {sip_cid_type=rpid}sofia/default/user@example.com (user@example.com) Send P-XXX-Identity {sip_cid_type=pid}sofia/default/user@example.com (user@example.com) Send RPID with chosen content {sip_cid_type=rpid,origination_caller_id_name=test,origination_caller_id_number=1234}sofia/default/user@example.com (user@example.com)



Send RPID with chosen content and privacy flags (+ delimited, none to clear all flags)
{sip_cid_type=rpid,origination_caller_id_name=test,origination_caller_id_number=1234,origination_privacy=screen+hide_name+hide_number}sofia/default/user@example.com (user@example.com)


[ Show » ]
user@example.com (user@example.com) Send RPID (default) {sip_cid_type=rpid}sofia/default/user@example.com (user@example.com) Send P-XXX-Identity {sip_cid_type=pid}sofia/default/user@example.com (user@example.com) Send RPID with chosen content {sip_cid_type=rpid,origination_caller_id_name=test,origination_caller_id_number=1234}sofia/default/user@example.com (user@example.com)




Also the privacy app on the inbound leg controls the remaining contents of the RPID and Privacy headers.


On Tue, Mar 10, 2009 at 7:32 AM, kokoska rokoska <kokoska.rokoska@post.cz (kokoska.rokoska@post.cz)> wrote:

[sicfslist at gmail.com]

Anthony,

That is awesome.  This is something that will be a BIG help.

SDR