[Dev] getting a sip SEP to work
Chasen, Les
les.chasen at neustar.biz
Wed Jun 6 17:14:44 EDT 2007
Try changing the priority to something different. There is a known bug
in xri.net that is fixed at beta.xri.net but can't be deployed until we
work through the final wd11 stuff.
contact: =les <http://xri.net/=les>
sip: =les/(+phone) <http://xri.net/=les/(+phone)>
chat: =les/skype/chat <http://xri.net/=les/skype/chat>
________________________________
From: dev-bounces at inames.net [mailto:dev-bounces at inames.net] On Behalf
Of Owen Davis
Sent: Wednesday, June 06, 2007 5:13 PM
To: Markus Sabadello
Cc: dev at inames.net
Subject: Re: [Dev] getting a sip SEP to work
I was hoping the fix would be that easy!
Unfortunately that doesn't work. :-(
http://xri.net/=ly/(+call)
behaves identically to
http://xri.net/=ly/+call
while what i want is behavior like
http://beta.xri.net/=ly/+call
On Jun 6, 2007, at 2:01 PM, Markus Sabadello wrote:
Hi,
It should be
http://xri.net/=ly/(+call)
not
http://xri.net/=ly/+call
Since you have (+call) in your <Path>
Markus
--
@freeXRI / freexri.com / try free i-names
On 6/6/07, Owen Davis <owen at linksafe.name> wrote:
I'm trying to add a SEP for sip to an XRDS. I've added the following
using the XRDS editor at Linksafe.
<xrd:Service priority="10">
<xrd:Type xrd:select="true">sip</xrd:Type>
<xrd:Path xrd:select="true">(+call)</xrd:Path>
<xrd:URI xrd:priority="1" xrd:append="none">sip:test at example.com</
xrd:URI>
</xrd:Service>
the result is mixed:
--> http://xri.net/=ly/+call fails and routes to my forwarding
service.
--> http://beta.xri.net/=ly/+call <http://beta.xri.net/=ly/+call>
succeeds. however i don't want
to use the beta resolver. =les.chasen seems to have the identical
XML working fine.
Does anyone know how to tweak my XRDS to work for the current resolver?
Thanks.
Owen
_______________________________________________
Dev mailing list
Dev at inames.net
http://dev.inames.net/mailman/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://dev.inames.net/pipermail/dev/attachments/20070606/8a0253c8/attachment.html
More information about the Dev
mailing list