Any time FreeSWITCH segfaults, you should file a JIRA. It would be nice if you could look at the backtrace and see if it happens in the same place or not, but if you're unable to read it, nobody will get mad about you filing a duplicate. It will just be noted as such and linked to the other. JIRAs are free, so when in doubt, fill it out :-)
-Ray
Finally, found success with mod_gsmopen. Have to say that there's a tonne of information in the Wiki, and it takes a newbie some time to get to understand even the elementary things. Jumping right in, assuming defaults to take care of everything, doesn't work. I believe that was thanks to being connected to the conference bridge 888@sip.freeswitch.net (if I noted the SIP URI correctly).Next tried another inbound call, and this time, I heard only silence.
Then I tried sending an SMS. That went out fine and was received instantaneously by the destination number. After that, I replied back to the dongle's number, and had a telnet session open listening on the events (none arrived), but that telnet session was closed, and turning to the FS console, I saw that it too had closed with a segmentation fault. So seems like receiving the SMS precipitated a core.
Anyone seen similar behaviour ? Should I go ahead an file another JIRA bugreport ? File one yesterday regarding another segmentation fault. Note, I am on Git HEAD (or was, day before, when I cloned it).
thanks,Jay
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org