El Miércoles, 3 de Marzo de 2010, Noble Antony T escribió:
> The suggestion/option seems to be useful/logical for that scenario you
> mentioned.
>
> As per RFC 3903,
>
> The presence of a body and the SIP-If-Match header field
> determine the specific operation that the request is performing,
> as described in Table 1.
> +-----------+-------+---------------+---------------+
>
> | Operation | Body? | SIP-If-Match? | Expires Value |
>
> +-----------+-------+---------------+---------------+
>
> | Initial | yes | no | > 0 |
> | Refresh | no | yes | > 0 |
> | Modify | yes | yes | > 0 |
> | Remove | no | yes | 0 |
>
> +-----------+-------+---------------+---------------+
>
> Table 1: Publication Operations
Thanks a lot for your reply. However my case doesn't appear in the table
above, as it should be:
+-----------+-------+---------------+---------------+
| Operation | Body? | SIP-If-Match? | Expires Value |
+-----------+-------+---------------+---------------+
| Initial | yes | no | 0 |
Anyhow it makes sense that it must be valid :)
Thanks.
--
Iñaki Baz Castillo <[email protected]>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
