Seven, thank you for the code!<div><br></div><div>I am just now starting to feel better and I will get back to work. You ideas are exactly what I have been putting in practice lately. Look at the accounts tab. Just add a widget where users can add or remove params. They gotta know the param names to be able to do that.</div>
<div><br clear="all">Joćo Mesquita<br>
<br><br><div class="gmail_quote">On Mon, Jan 11, 2010 at 3:48 AM, Seven Du <span dir="ltr"><<a href="mailto:dujinfang@gmail.com">dujinfang@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks, see inline comments:<br>
<br>
2010/1/11 Joćo Mesquita <<a href="mailto:jmesquita@freeswitch.org">jmesquita@freeswitch.org</a>>:<br>
<div class="im">><br>
> Forgot to reply line by line ...<br>
><br>
> Joćo Mesquita<br>
><br>
><br>
> On Sun, Jan 10, 2010 at 2:12 PM, Seven Du <<a href="mailto:dujinfang@gmail.com">dujinfang@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> FsComm is really cool. I played and make some improvements, see<br>
>> rev16229 in trunk(in my contrib dir). And note is stll has bugs when<br>
>> sometimes the sound dev list doesn't sync well with FScomm on some<br>
>> edge cases. Also ideally it can be automatically updated like XLite.<br>
>><br>
>> Because I cannot join the last weekly conference due to network<br>
>> problems so I don't know the results been discussed. Questions?<br>
>><br>
>> 1) When will we have jira for this?<br>
>> 2) What the next step of FsComm dev?<br>
><br>
> Have the Sofia accounts configuration pane and right after that, process the<br>
> events correctly. There are a lot of flaws on how I deal with them at the<br>
> moment.<br>
><br>
>><br>
>> 3) My time doesn't match well with most of you, so, hard to chat on<br>
>> IRC. Even we have jira for this it would be a pain if I want to commit<br>
>> more patches. Is that ok I commit to my contrib and someone merge to<br>
>> trunk?<br>
><br>
> I would love if you could post patches on Jira instead with the work you see<br>
> fit. Otherwise, I will easily loose track of things.<br>
><br>
<br>
</div>ok, will do. Someone contribute Paypal and I would like to contribute<br>
code. Ideally there be a feature list on wiki or roadmap on jira we<br>
can follow to avoid invent wheels at the same time, something like<br>
this:<br>
<br>
goal:<br>
<br>
As Brian described on list:<br>
<br>
Easy to use, a really nice phone with lots of options, would be kick ass.<br>
Must work on 32bit and 64bit of Windows, Mac and Linux ... and not<br>
suck like most softphones do.<br>
<br>
features:<br>
<br>
* manually register/unregister for each accounts, very useful for<br>
debugging, as in Zoiper<br>
* easy dial out through different gateways<br>
* auto reconfigure sound devices when dev changes(say a USB headset<br>
pluged/unpluged, as in XLite)<br>
* Just found a good feature list as I'm writing this list:<br>
<a href="http://www.zoiper.com/feature_list_zoiper_communicator.php" target="_blank">http://www.zoiper.com/feature_list_zoiper_communicator.php</a> and it<br>
would be cool if all "BIZ ONLY" features can be replaced by "FREE" :)<br>
<br>
Despite the rich features, we should also make it *Extremely* easy to<br>
use for non-technical people, E.g. for sip gateway config it only<br>
needs username/password/realm, all other params should be in<br>
Advanced/Ad-Advanced conf ...<br>
<div class="im"><br>
<br>
>><br>
>> 4) Is it possible I commit to trunk? Then how to do code review before<br>
>> commit? It's the first time I program QT so some code must be very<br>
>> ugly.<br>
>><br>
><br>
> The question above replies this one too. Time will get you to trunk. :-)<br>
><br>
>><br>
>> Some bugs I found:<br>
>><br>
>> 1) FreeSWITCH/FsComm user agent breaks xml parser, complains missing<br>
>> ">", I guess it's a XML parser bug when it see "/" it expects an ">"<br>
>> to be a "/>". Sorry I deleted the full log but I think it can be<br>
>> replicated so let me know if I need to report to jira.<br>
>><br>
><br>
> Please do. This is a bug in switch_event_expand_headers() and I haven't yet<br>
> had the time to figure out what is the char that breaks it.<br>
><br>
>><br>
>> 2) I change event_socket.conf.xml to use port 8022 to avoid conflict<br>
>> with another FS instance. 10% of times I run FsComm it cannot been<br>
>> read.<br>
><br>
> The idea is to disable this after some time since it makes no sense at all<br>
> to be there other then debugging. So I guess you can do whatever with that<br>
> template.<br>
><br>
<br>
</div>For debugging and for fan, I'd like to keep it. Provide an api allow<br>
people make better use of it. Also I noticed API is a "BIZ ONLY"<br>
feature on <a href="http://www.zoiper.com/feature_list_zoiper_communicator.php" target="_blank">http://www.zoiper.com/feature_list_zoiper_communicator.php</a><br>
<div><div></div><div class="h5"><br>
>><br>
>> 2010-01-10 23:35:53.631687 [DEBUG] mod_qsettings.cpp:80 Template<br>
>> event_socket.conf as follows:<br>
>> <document type="freeswitch/xml"><br>
>> <section name="configuration"><br>
>> <configuration name="event_socket.conf" description="Socket Client"><br>
>> <settings><br>
>> <param name="nat-map" value="false"/><br>
>> <param name="listen-ip" value="127.0.0.1"/><br>
>> <param name="listen-port" value="8022"/><br>
>> <param name="password" value="ClueCon"/><br>
>> </settings><br>
>> </configuration><br>
>> </section><br>
>> </document><br>
>> 2010-01-10 23:35:53.631490 [ERR] mod_qsettings.cpp:62 Template<br>
>> post_load_switch.conf could not be read!<br>
>> 2010-01-10 23:35:53.631799 [ERR] mod_event_socket.c:2543 Open of<br>
>> event_socket.conf failed<br>
>> 2010-01-10 23:35:53.631918 [ERR] mod_event_socket.c:2639 Socket Error!<br>
>> Could not listen on <a href="http://127.0.0.1:8021" target="_blank">127.0.0.1:8021</a><br>
>> 2010-01-10 23:35:53.732089 [ERR] mod_event_socket.c:2639 Socket Error!<br>
>> Could not listen on <a href="http://127.0.0.1:8021" target="_blank">127.0.0.1:8021</a><br>
>><br>
>> Cheers.<br>
>><br>
>> Seven.<br>
>><br>
>> _______________________________________________<br>
>> FreeSWITCH-dev mailing list<br>
>> <a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
>> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
>> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
>> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
><br>
><br>
> _______________________________________________<br>
> FreeSWITCH-dev mailing list<br>
> <a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
><br>
><br>
<br>
_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br></div>