[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sipping] XCAP server discovery



The xcap root services URI should be one of many parameters passed to the client through the configuration framework:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-06.txt

-Jonathan R.

Arjun Roychowdhury wrote:

Hi,
most implementations I know of today provision the UA with the XCAP
services root URI. Once the root URI is known, since XCAP mandates
that documents are organized according to a defined hierarchy, the UA
can then navigate to the exact service that is required.

I am personally not aware of any best practices to dynamically
identify the XCAP URI but I guess something like ${domain}/services
may not be a bad idea where ${domain} is the domain that is servicing
the User Agent.

regds
arjun


On 6/18/05, Jeroen van Bemmel <jbemmel at zonnet.nl> wrote:

Hi,

Suppose one would make a useragent that uses SIP for presence and XCAP for
manipulation of buddy lists etc. , what would be the best way to provision
the client with the URL of its XCAP server?

Regards,

Jeroen



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP





-- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Director, Service Provider VoIP Architecture Parsippany, NJ 07054-2711 Cisco Systems jdrosen at cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP