[Serusers] commercial help requested

[Jiri Kuthan]

At 17:57 05/02/2008, Kenneth wrote:
>Jiri,
>
>Thanks for the quick response.
>
>It may be a bit more complicated than just the P-asserted header.

ok. Well  I don't have specific recommendation (we actually never needed 
a SER support organization :-)) other than serdev if you need more intense
support.

>It seems that we do not have anyone that knows the SER, and we want to set it up as one of the elements in our network. The party we are sending to will not test before we can provide header copies containing the P-asserted header as follows:
>
>3.17    ANI (Calling Party Number) Delivery
>Following is a list of basic requirements regarding ANI Delivery:
>
>ANI / Calling Party Number delivery is per RFC3325 (P-Asserted-Id Header).
>XYZ Company will pass the ANI in the P-Asserted-Id Header or Remote Party ID (SIP Gateway only) header to the customer. 
>The customer must send a valid ANI in the P-Asserted-Id or Remote Party ID (SIP Gateway only) to XYZ Company, otherwise the call will be blocked. 
>
>Acceptable formats are as follows:
>
>P-Asserted-Identity: "John Doe" <sip:+17034633348 at 100.0.0.1;user=phone>
>P-Asserted-Identity: <sip:+17034633348 at 100.0.0.1;user=phone>
>P-Asserted-Identity: <sip:+17034633348 at 100.0.0.1>
>
>     Please attach a sample SIP trace to confirm P-Asserted ID or Remote Party ID Header support.

see ser-oob.cfg

    # if an optional AVP 'asserted_id' is set we insert an RPID header
    if ($asserted_id) {
        xlset_attr("$rpidheader", "<sip:%$asserted_id@%@ruri.host>;screen=yes");
        replace_attr_hf("Remote-Party-ID", "$rpidheader");
    }

you would just need to update the formatting string and the header field name. 


-jiri



>3.18    Caller Privacy Mechanism
>Following is a list of basic requirements regarding Caller Privacy (blocking of Caller ID info delivery):
>
>Caller Privacy per RFC3325 (P-Asserted-Id).
>XYZ Company will pass the P-Asserted-Id and Privacy Headers to the customer.  
>The customer must send a valid ANI in the P-Asserted-Id and optionally a Privacy Header to XYZ Company, otherwise the call will be blocked. 
>Using Remote Party ID, customer must set RPI-screen to Full or URI in the header
>The customer should set the From header to “anonymous” and set the Privacy Header to “id” if privacy is required.
>
>Example: 
>
>Privacy: none   (deliver calling number)
>Privacy: id             (block calling number)
>
>I need someone who can help us set up a SER with this and, of course we will pay for the service.
>
>Any recommendations you can give will be greatly appreciated.
>
>Kenneth 
>
>-----Original Message-----
>From: Jiri Kuthan [mailto:jiri at iptel.org] 
>Sent: Tuesday, February 05, 2008 9:13 AM
>To: kenneth.hosfeld at interlink-global.com; serusers at iptel.org
>Subject: Re: [Serusers] commercial help requested
>
>I think this is easier than you may think -- why don't you look at the oob.cfg file,
>it does RemotePartyID which is close to P-asserted-header, at least SER-wise.
>It takes the telephone number from user profile and appends it properly
>formatted to the forwarded request.
>
>-jiri
>
>At 21:49 04/02/2008, Kenneth wrote:
>>We need someone who can quickly assist us with creating the P-asserted header on SER. RFC 3325. Configuration.
>> 
>>If there is an expert out there, please contact us with your qualifications and rates.
>> 
>>Kenneth 
>> 
>>_______________________________________________
>>Serusers mailing list
>>Serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
>--
>Jiri Kuthan            http://iptel.org/~jiri/



--
Jiri Kuthan            http://iptel.org/~jiri/