[SIP Beyond VoIP] Another case where Sylk would reject Notifications

[Adrian Georgescu]

On Nov 15, 2012, at 2:34 PM, Hadzhiev, Tihomir wrote:

>  
> 4.       Sylk will accept the NOTIFY with 200 OK and will reply correctly towards IMS Core -> Presence Server.
>  
> Now the problem here is that SYLK won’t generate a Presence Stanza towards the XMPP server. Looking at the web site’s sequence diagram, Sylk would expect a Subscribe,

I think you are confused a bit here. SylkServer got the Notify from SIP as a result of his own Subscribe generated as a result of the XMPP subscription being active. The payload if parsed correctly will trigger an XMPP stanza update back to XMPP world. If this does not happen there should be some exception in the logs.


> which of course won’t be sent from the IMS client if a network address book is used.

I speculate that what you call a "network address book "is the Presence Agent RLS function that must expand the resource-list uploaded by the SIP client into URIs and subscribe to them. 

This RLS server must send the Subscribe  in behalf of its own users and for those that end up in XMPP world must be routed to sylkServer. If it does not do this you must fix it.

> 
> So my question is, is there something that could be done in that case?  I can simulate the SUBSCRIBE of course, e.g. to have the IMS client sending SUBSCRIBE towards the XMPP domain, however I know this is not working ( the problem I have reported yesterday ).

Your IMS server (its RLS component) must generate the Subscriptions for each individual URI uploaded by the SIP client in the XCAP resource lists document. 

>  
> Thanks,
> Tiho
> 
> This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
> 
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20121115/0e577196/attachment.html>