<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 05 Jan 2016, at 00:47, Adrian Weiler <<a href="mailto:sylk-testing@aweiler.com" class="">sylk-testing@aweiler.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hello again,<br class=""><br class="">At 04.01.2016, 17:31 Adrian Georgescu wrote:<br class=""><blockquote type="cite" class="">There is nothing special in SylkServer that can make it work only with a particular SIP Proxy. It should work with any proxy or without one.<br class=""></blockquote>SylkServer does not provide accounts. If I configure an account with a<br class="">domain whose _sips._tcp DNS record points directly to SylkServer, the<br class="">server will reject the initial PUBLISH, REGISTER and SUBSCRIBE requests<br class="">with 405 Method Not Allowed and 489 Bad Event. So IMHO I do need a proxy.<br class=""><br class="">If you claim that SylkServer works without proxy, then please provide<br class="">some documentation on how that should be configured.<br class=""></div></blockquote><div><br class=""></div><div>Well, is zero configuration really. Your SIP client starts a session by sending an INVITE to SylkServer, there is nothing you need to configure for this to work.</div><div><br class=""></div><div>If in doubt that your proxy is the culprit just start a session from Blink to SylkServer like <a href="mailto:user@sylkserver.ip.address" class="">user@sylkserver.ip.address</a></div><div><br class=""></div><div>Than do the same while traversing your proxy see what the difference is and fix the proxy configuration.</div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class=""><br class=""><blockquote type="cite" class="">Your proxy must relay all packets between the two rather than blocking them, this is is something configured into your SIP Proxy.<br class=""></blockquote>If the proxy is configured to relay *all* packets, then I get the same<br class="">405 and 489 results as when having no proxy at all. So the proxy is<br class="">supposed to do some work of its own, but probably in a different way<br class="">than how it is implemented by reSIProcate.</div></blockquote></div><div><blockquote type="cite" class=""><div class=""><br class="">Please answer my question: which proxies is SylkServer known to work with?<br class=""></div></blockquote><div><br class=""></div><div>For example OpenSIPS is used by sip2sip.info</div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class="">You can also point Blink to SylkServer directly or using Bonjour mode in Mac you can discover it automatically and use it.<br class=""></blockquote>I don't have a Mac. What do you mean with "point Blink to SylkServer"?<br class="">The conference contact *is* defined for the domain pointing to<br class="">SylkServer. The option "Always use my proxy for outgoing sessions" is<br class="">*not* set. But Blink always talks to the domain where the account is<br class="">defined, not to the contact's domain.<br class=""></div></blockquote><div><br class=""></div><div>You can dial from Blink any SIP URI like room@sylkserver_ip without traversing your proxy.</div><br class=""><blockquote type="cite" class=""><div class=""><br class="">Regards,<br class="">Adrian Weiler<br class="">_______________________________________________<br class="">SIPBeyondVoIP mailing list<br class=""><a href="mailto:SIPBeyondVoIP@lists.ag-projects.com" class="">SIPBeyondVoIP@lists.ag-projects.com</a><br class="">http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip<br class=""><br class=""></div></blockquote></div><br class=""></body></html>