2010/5/28 Daniel-Constantin Mierla <[email protected]>:
> Hello,
>
> I added an XCAP server (supports basic operations by now) to open source
> SIP servers Kamailio (OpenSER) and SIP Express Router (SER).
>
> Being embedded in the SIP server makes possible to transmit the XCAP
> documents via SIP (UDP, TCP, TLS, SCTP) as well -- HTTP/S support is
> there, but might be useful for (custom) phone implementations that don't
> have a HTTP client stack.

Hi, in XCAP there are 4 HTTP methods: GET, PUT, DELETE and POST (POST
is just used in OMA search application).
How are these HTTP method supposed to be mapped into SIP?


> My first question is related to the XCAP doc URL, since the SIP URI is
> pretty different than HTTP, using a special header would be a better
> alternative? ie,:
>
> XCAP-URL: /xcap-root/pres-rules/users/alice/index

And then which SIP method would be used?


> Also, what request type to use for transporting the documents? There was
> a draft extending SIP REGISTER to carry payloads:
> http://tools.ietf.org/html/draft-lennox-sip-reg-payload-01

IMHO an easier approach would be defining a new SIP method (i.e.
"XCAP") and adding two headers for XCAP action and uri). Then the
content type would be the same as in current XCAP/HTTP specification:


XCAP sip:presence-server.org SIP/2.0
XCAP-Action: PUT
XCAP-URI: /pidf-manipulation/users/sip:[email protected]/index
SIP-If-Match: qweqweqweqweqwe
Content-Type: application/pidf+xml
...

<?xml version="1.0" encoding="UTF-8"?>
        <presence xmlns="urn:ietf:params:xml:ns:pidf"
             xmlns:rp="urn:ietf:params:xml:ns:pidf:rpid"
             xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
             xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
             entity="sip:[email protected]">

          <tuple id="x8eg92m">
            <status>
              <basic>closed</basic>
            </status>
            <rp:user-input>idle</rp:user-input>
            <rp:class>auth-1</rp:class>
            <contact priority="0.5">sip:[email protected]</contact>
            <note>I'm available only by e-mail.</note>
            <timestamp>2004-02-06T16:49:29Z</timestamp>
          </tuple>
       </presence>


Note also that XCAP uses "Etag", "If-Match" and "If-None-Match" HTTP
headers which hav their equivalent in SIP ("SIP-xxxx").

-- 
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to