VoIP Mailing List Archives

[fdhege at gmail.com]

Hello again,

I wanted to first say thanks to Brain for helping me fix my from
domain issue the other day. It helped quite a bit.

Now with more testing and talking with the vendor (please don't shoot
the messenger )

They want the caller id info in the from and the charge number/
screening number in the P-Asserted-ID.

I have tested this and verified that this does work like they say it
does by setting the callerid number to my charge number and setting
the from user in the gateway config to the callerid I want displayed.
But this solution doesn't scale very well.

I know I can set the gateway option caller-id-in-from to get that part
done. But is there a way to set the P-Asserted-ID to something other
than the callerid?

Any hints would be welcomed.

Thanks,

-Dale

_______________________________________________
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]

On Jul 16, 2009, at 9:30 AM, Dale wrote:

[krice at suspicious.org]

That's just right down screwing with the standards...

PAID is the caller id... This particular definition is from the RFCs and
3GPP docs for IMS which is why we have standardized P- headers...

Can your vendor not look at the P-Charging-Vector field?

Also, From when used with PAID is more like an ANI not a CLID

[dave at 3c.co.uk]

Hi Dale,

You can set the header to anything you like by including something along
the lines of
<action application="set" data="sip_h_P-Asserted-Identity=<sip:
${caller_id_number}@1.2.3.4>" />
in your dialplan.

Cheers --

Dave

[fdhege at gmail.com]

That works perfectly.

Thanks,

-Dale

On Jul 16, 2009, at 10:37 AM, Brian West wrote:

[brian at freeswitch.org]

Kinda wrong there!

Gotta use CDATA because it has < and > in the data you're setting. And you'll wanna export it I suspect.


<action application="export"><![CDATA[sip_h_P-Asserted-Identity=<[url=sip:$]sip:$[/url]{caller_id_number}@1.2.3.4>]]></action>


/b





On Jul 16, 2009, at 9:51 AM, David Knell wrote:

[fdhege at gmail.com]

Who knows. I have asked why they are backwards when it comes to the
RFC's.

-Dale

On Jul 16, 2009, at 10:41 AM, Ken Rice wrote:

[fdhege at gmail.com]

Hey, you happen to have the RFC number and section they are violating?

I'll dig it up. But figured I'd ask since you all seem to have them
memorized by now.

-Dale

On Jul 16, 2009, at 10:41 AM, Ken Rice wrote:

[sicfslist at gmail.com]

PAI is defined @ http://www.ietf.org/rfc/rfc3325.txt

For what they are trying to do Sonus suggested P-Charge-Info (which I think it is still in the draft stage) --> http://www.ietf.org/internet-drafts/draft-york-sipping-p-charge-info-06.txt

[dave at 3c.co.uk]

Really? That line (+/- the IP address) came directly out of a working
dialplan. To be fair, the box is running a faintly prehistoric
FreeSWITCH - you crazy cats haven't been chewing on the tail of my
cherished mouse of backwards compatibility again, have you?!

What has been incorrect in this discussion is the name of the header:
it's P-Asserted-Identity, not P-Asserted-ID. The fact that it's usually
shortened to PAID doesn't help; nor does the fact that Remote-Party-ID
(which is deprecated, but still widely used for the same job as
P-Asserted-Identity) is about as well.

--Dave

[brian at freeswitch.org]

Not sure how you were able to set the variable with < and > in it at
all thats not been possible cuz the XML parser will barf on it usually.

/b

On Jul 16, 2009, at 2:20 PM, David Knell wrote:

[fdhege at gmail.com]

Hmm, it seems to work on a copy of trunk from a few days ago. Both
in the dialplan and the gateway config.

But I could see how that might cause a problem with the xml.

-Dale

On Jul 16, 2009, at 3:27 PM, Brian West wrote:

[msc at freeswitch.org]

I think the parser is probably supposed to barf on consecutive < chars but it doesn't. I learned that the hard way when I left the closing tag off of an action in the dp. Consider this dp snippet:

<action application="log" data="INFO Now you see me"
<action application="log" data="INFO Now you don't"/>
<action application="log" data="INFO Now you see me"/>

The above works but the 2nd log does not display. Just an FYI.
-MC

On Thu, Jul 16, 2009 at 12:42 PM, Dale <fdhege@gmail.com (fdhege@gmail.com)> wrote:

[krice at suspicious.org]

Hey Dale RFC4694 defines how to pass JIP LRN and CIC (and a few other
things) as part of the tel URI... This has been adapted for use in SIP as
the user part of the invite and from URIs... Theres also RFC3325 for PAID
and if you check out the wikipedia page for IMS (IP Multimedia Subsystem)
there are several other RFCs that are related for various "P headers" there.
Most of these headers come out from the 3GPP/IMS working groups