Hi Adrian,<br><br>Yes, the sipsimpleclient library searches for those wavs relatively from the location of the client programs. I made a symbolic link to /usr/share to overcome that.<br>From the location of the client programs, the library is looking in ../share/sipclient/ for the wav files. So if you unpacked the tgz in /home/adrian/desktop_sharing/ and thus the programs are in /home/adreian/desktop_sharing/sip_desktop_sharing-0.02/ you can make a symbolic link with:<br>
<br>ln -s /usr/share /home/adreian/desktop_sharing/share<br><br>Good luck,<br><br>Willem<br><br><div class="gmail_quote">2009/1/25 Adrian Georgescu <span dir="ltr"><<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">Hi Willem,<div><br></div><div><br></div><div>I am getting an exception on both sides when I try to establish the desktop sharing session scripts, it seems that the programs cannot find the ringing wav files to play. </div>
<div><br></div><div>Initiating SIP session from "Adrian G." <<a>sip:31208005169@ag-projects.com</a>> to <a>sip:ag@ag-projects.com</a> through proxy 85.17.186.7:5060...</div><div><div>Early SIP session to <a>sip:ag@ag-projects.com</a> (180 Ringing)</div>
<div>Ringing from <a>sip:31208005169@80.101.96.20:61385</a></div><div>Traceback (most recent call last):</div><div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/hubs/twistedr.py", line 246, in run</div>
<div> self.mainLoop(reactor)</div><div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/hubs/twistedr.py", line 264, in mainLoop</div><div> reactor.runUntilCurrent()</div><div>--- <exception caught here> ---</div>
<div> File "/Library/Python/2.5/site-packages/Twisted-8.1.0-py2.5-macosx-10.5-i386.egg/twisted/internet/base.py", line 705, in runUntilCurrent</div><div> call.func(*call.args, **<a href="http://call.kw" target="_blank">call.kw</a>)</div>
<div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/proc.py", line 503, in _run</div><div> result = function(*args, **kwargs)</div><div> File "/Library/Python/2.5/site-packages/pypjua/enginebuffer.py", line 257, in _run</div>
<div> self.play_wav(*self.args, **self.kwargs)</div><div> File "core.ua.pxi", line 405, in pypjua.core.PJSIPUA.play_wav_file (pypjua/core.c:16132)</div><div> </div><div> File "core.sound.pxi", line 260, in pypjua.core.WaveFile.__cinit__ (pypjua/core.c:8411)</div>
<div> </div><div>pypjua.core.PJSIPError: Could not open WAV file: Not found (PJ_ENOTFOUND)</div><div>Traceback (most recent call last):</div><div> File "./sip_offer_desktop", line 87, in <module></div>
<div> main()</div><div> File "./sip_offer_desktop", line 72, in main</div><div> session = MSRPSession.invite(inv, msrp_connector, make_make_RFB_SDPMedia(desktop_request), ringer=ringer)</div><div> File "/Library/Python/2.5/site-packages/pypjua/clients/msrpsession.py", line 96, in invite</div>
<div> invite_response, msrp = invite(inv, msrp_connector, SDPMedia_factory, ringer)</div><div> File "/Library/Python/2.5/site-packages/pypjua/clients/msrpsession.py", line 46, in invite</div><div> invite_response = inv.invite(ringer=ringer)</div>
<div> File "/Library/Python/2.5/site-packages/pypjua/enginebuffer.py", line 436, in invite</div><div> event_name, params = q.wait()</div><div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/coros.py", line 1034, in wait</div>
<div> self.sem.acquire()</div><div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/coros.py", line 302, in acquire</div><div> api.get_hub().switch()</div><div> File "/Library/Python/2.5/site-packages/eventlet-0.9pre-py2.5.egg/eventlet/hubs/twistedr.py", line 227, in switch</div>
<div> return self.greenlet.switch()</div><div>eventlet.proc.LinkedFailed: '<bound method Ringer._run of <pypjua.enginebuffer.Ringer instance at 0x2a06d78>>' failed with PJSIPError</div><div><br></div>
<div>Regards,</div></div><div>Adrian</div><div><br><div><div><div></div><div class="Wj3C7c"><div>On Jan 24, 2009, at 11:46 PM, Willem Toorop wrote:</div><br></div></div><blockquote type="cite"><div><div></div><div class="Wj3C7c">
Hi Adrian, Michiel, Ruud & Denis,<br><br>Attached is a version that actually works quiet well. It is slow, but usable (less then a second response time). Cleanups are handled nicely (no crashing scripts) and they use the "m=application <port> TCP/TLS/MSRP/RFB *" media line in the SDP.<br>
<br>While debugging packet order, going in and out, I noticed that sometimes an empty MSRP message is received, although the Byte-Range header indicates differently. Once those messages were filtered out, everything started working fine.<br>
<br>Here is such a message:<br><br><font face="courier new,monospace">MSRP BnWVQ0OmGQBNgqMYT3KqvlYR SEND<br>To-Path: msrps://<a href="http://192.168.178.33:38731/b4APciEdQfmw;tcp" target="_blank">192.168.178.33:38731/b4APciEdQfmw;tcp</a><br>
From-Path: msrps://<a href="http://node03.dns-hosting.info:2855/k5yd231nlUJOLUXKR1yz0DEyMzI4MzYwOTAuNjU5OjgyLjk1LjE0MS4xMjc=;tcp" target="_blank">node03.dns-hosting.info:2855/k5yd231nlUJOLUXKR1yz0DEyMzI4MzYwOTAuNjU5OjgyLjk1LjE0MS4xMjc=;tcp</a> msrps://<a href="http://node03.dns-hosting.info:2855/R0g1LsWuyTYghdQyDUIcOzEyMzI4MzYwODguNzI0OjgyLjk1LjE0MS4xMjc=;tcp" target="_blank">node03.dns-hosting.info:2855/R0g1LsWuyTYghdQyDUIcOzEyMzI4MzYwODguNzI0OjgyLjk1LjE0MS4xMjc=;tcp</a> msrps://<a href="http://192.168.178.33:38730/YFdsfYLisv1V;tcp" target="_blank">192.168.178.33:38730/YFdsfYLisv1V;tcp</a><br>
Message-ID: vRlGOYQEyF<br>Byte-Range: 1-42/42<br>Content-Type: application/x-rfb<br><br><br>-------BnWVQ0OmGQBNgqMYT3KqvlYR+<br></font><br>The + on the end of the end-line<transaction id> indicates that more is coming, but in that case the Byte-Range should have been 1-*/42 (i think, because 1-1/42 would incidate one byte of data and 1-0/42 is just silly), or the message should not have been sent at all.<br>
<br>So I was wrong thinking that the order of the messages was altered by MSRP-Relay. The garbage I saw in earlier versions where due to receiving those MSRP messages with no content; The socket connecting to the viewer was closed by them halfway in an update of several rectangles. When the connection was closed, the rectangles on the screen would be updated with data that was already in the buffer where the update data should have been loaded.<br>
MSRP-Relay is forwarding the messages in the order it received it in.<br><br>Sorry about the confusion.<br>Cheers,<br><br>Willem<br><br> </div></div><span><sip_desktop_sharing-0.02.tgz></span></blockquote></div><br>
</div></div><br>_______________________________________________<br>
SIPclient mailing list<br>
<a href="mailto:SIPclient@lists.ag-projects.com">SIPclient@lists.ag-projects.com</a><br>
<a href="http://lists.ag-projects.com/mailman/listinfo/sipclient" target="_blank">http://lists.ag-projects.com/mailman/listinfo/sipclient</a><br>
<br></blockquote></div><br>