[Freeswitch-dev] Fscomm status and issues and patch

João Mesquita jmesquita at freeswitch.org
Sun Jan 10 18:45:11 PST 2010

Forgot to reply line by line ...

João Mesquita

On Sun, Jan 10, 2010 at 2:12 PM, Seven Du <dujinfang at gmail.com> wrote:

> Hi,
> FsComm is really cool. I played and make some improvements, see
> rev16229 in trunk(in my contrib dir). And note is stll has bugs when
> sometimes the sound dev list doesn't sync well with FScomm on some
> edge cases. Also ideally it can be automatically updated like XLite.
> Because I cannot join the last weekly conference due to network
> problems so I don't know the results been discussed. Questions?
> 1) When will we have jira for this?
> 2) What the next step of FsComm dev?

Have the Sofia accounts configuration pane and right after that, process the
events correctly. There are a lot of flaws on how I deal with them at the

> 3) My time doesn't match well with most of you, so, hard to chat on
> IRC. Even we have jira for this it would be a pain if I want to commit
> more patches. Is that ok I commit to my contrib and someone merge to
> trunk?

I would love if you could post patches on Jira instead with the work you see
fit. Otherwise, I will easily loose track of things.

> 4) Is it possible I commit to trunk? Then how to do code review before
> commit? It's the first time I program QT so some code must be very
> ugly.
The question above replies this one too. Time will get you to trunk. :-)

> Some bugs I found:
> 1) FreeSWITCH/FsComm user agent breaks xml parser, complains missing
> ">", I guess it's a XML parser bug when it see "/" it expects an ">"
> to be a "/>". Sorry I deleted the full log but I think it can be
> replicated so let me know if I need to report to jira.
Please do. This is a bug in switch_event_expand_headers() and I haven't yet
had the time to figure out what is the char that breaks it.

> 2) I change event_socket.conf.xml to use port 8022 to avoid conflict
> with another FS instance. 10% of times I run FsComm it cannot been
> read.

The idea is to disable this after some time since it makes no sense at all
to be there other then debugging. So I guess you can do whatever with that

> 2010-01-10 23:35:53.631687 [DEBUG] mod_qsettings.cpp:80 Template
> event_socket.conf as follows:
> <document type="freeswitch/xml">
>    <section name="configuration">
> <configuration name="event_socket.conf" description="Socket Client">
>          <settings>
>                <param name="nat-map" value="false"/>
>                <param name="listen-ip" value=""/>
>                <param name="listen-port" value="8022"/>
>                <param name="password" value="ClueCon"/>
>          </settings>
>    </configuration>
>  </section>
> </document>
> 2010-01-10 23:35:53.631490 [ERR] mod_qsettings.cpp:62 Template
> post_load_switch.conf could not be read!
> 2010-01-10 23:35:53.631799 [ERR] mod_event_socket.c:2543 Open of
> event_socket.conf failed
> 2010-01-10 23:35:53.631918 [ERR] mod_event_socket.c:2639 Socket Error!
> Could not listen on
> 2010-01-10 23:35:53.732089 [ERR] mod_event_socket.c:2639 Socket Error!
> Could not listen on
> Cheers.
> Seven.
> _______________________________________________
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20100110/ecad851a/attachment.html 

More information about the FreeSWITCH-dev mailing list