I sent following message:
PUBLISH sip:[remote_ip] SIP/2.0 Via: SIP/2.0/[transport] [local_ip]:[local_port] To: sip:[field0]@[remote_ip]:[remote_port] From: <sip:[field0 file="auth.csv"]@[remote_ip]:[remote_port]> Contact: sip:[field0]@[local_ip]:[local_port];transport=[transport] Expires: 300 Call-ID: [call_id] CSeq: 1 PUBLISH Content-Type: application/xhttp Content-Length: [len]
PUT /xcap-root/pres-rules/users/ravi_p_test_com@50.62.1.7/indexHTTP/1.1 Content-Type: application/auth-policy+xml User-Agent: Ruby-XCAPClient/1.4.1 If-Match: "sr-1316728844-17029-98" Connection: close Content-Length: 926 Host: 50.62.1.7:5060 Date: Thu, 22 Sep 2011 22:23:22 GMT
<?xml version="1.0"?>pr:rulesets xmlns:cp="urn:ietf:params:xml:ns:common-policy" xmlns:pr="urn:ietf:params:xml:ns:pres-rules" cp:rules id="pres_whitelist" cp:conditions cp:identity <cp:one id=" 1krishna_b_test_com@50.62.1.7"/> </cp:identity> </cp:conditions> </cp: rules></pr:rulesets>
I used sipp to simulate. Let me know if this it eh correct format. I am receiving 407 and the sipp script is failing to respond to it.
Krish
On Thu, Sep 22, 2011 at 2:25 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
Hello,
On 9/22/11 9:14 PM, Krishna Kurapati wrote:
Hi,
The document http://kb.asipto.com/kamailio:presence:k31-made-simple
describes that XCAP can be sent over SIP instead of over HTTP. I tried to do however, the server is unable to update presence rules. I was using PUBLISH method. I was using content-type = text...
content type does not really matters from internal point of view for embedded xcap server.
Has anyone used SIP to send over XCAP? Appreciate if someone could share a link or configuration changes required.
What errors do you get?
It is practically a matter of xcaps_put() parameters. You have to provide the SIP URI for user, the path of the xcap document and the content of the xcap document. How you used this function?
Cheers, Daniel
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda