I have built FSComm on Windows with Visual Studio 2008. I am able to register my VoIP service provider, but I am receiving an error "NO_ROUTE_DESTINATION" when trying to call my home number with "0019876543210". I have tried FreeSwitch with X-Lite before and was able to make the same call. I am wondering where I need to modify my configuration so that I can make a similar call. Any screen print or example of calling is welcome.
Paul, I found the problem. It can be divided into 2 parts. 1. I was not setting the default account to be used This is fixed now on rev: 16346 but new GUI changes will be made so we are able to select the default account to be used and also display what account is the default one. 2. mod_portaudio had a bug of setting the default dialplan module to the string "default" which is plain wrong, and we were not overwriting it on FSComm's settings module, causing it to simply, silently, not route the call. This has been fixed on rev: 16345 To get these changes working, you will need to recompile mod_portaudio and FSComm. Thank you for your interest in the project and sorry for the long time to fix that, afterall, it is weekend. Regards, João Mesquita FSComm Developer On Sun, Jan 17, 2010 at 5:35 AM, Paul Li <plite2012@gmail.com> wrote:
I have built FSComm on Windows with Visual Studio 2008. I am able to register my VoIP service provider, but I am receiving an error "NO_ROUTE_DESTINATION" when trying to call my home number with "0019876543210". I have tried FreeSwitch with X-Lite before and was able to make the same call. I am wondering where I need to modify my configuration so that I can make a similar call.
Any screen print or example of calling is welcome.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
João, thank you very much. It is now working like a charm. One small typo is about a normal clearing, "Call with (5000) failed with reason NORMAL_CLEARING", which I believe should be "Call with (5000) ended with ...", as this is not an error. I have one more question on how to tie a remote endpoint to the default IVR at Ext 5000. I used to use the originate command, such as originate sofia/default/1008%192.168.4.151 5000 so that the remote endpoint will be bridged to the announcement at Ext 5000. How can I do this in FSComm?
Paul, I am not sure I understood your question. Can you elaborate a little bit better? Also, the code you have right now is buggy and I am working at it as we speak. Right now, settings are not correctly persisted for some reason. I was working on a patch posted on Jira because I didn't want code to move a lot further and make it harder to merge later on. Please be patient since this is a very new project. Also, if you want a more live conversation, you can join #fscomm @ freenode. I am always there. Regards, João Mesquita FSComm Developer On Mon, Jan 18, 2010 at 12:34 AM, Paul Li <plite2012@gmail.com> wrote:
João, thank you very much. It is now working like a charm. One small typo is about a normal clearing, "Call with (5000) failed with reason NORMAL_CLEARING", which I believe should be "Call with (5000) ended with ...", as this is not an error.
I have one more question on how to tie a remote endpoint to the default IVR at Ext 5000. I used to use the originate command, such as
originate sofia/default/1008%192.168.4.151 5000
so that the remote endpoint will be bridged to the announcement at Ext 5000. How can I do this in FSComm?
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Paul, Just had the commit that really makes things work (16350<http://fisheye.freeswitch.org/changelog/FreeSWITCH?cs=16350> ). If not, please report. Recompile FSComm and you will get new features on it as well contributed by Seven. Regards, João Mesquita FSComm Developer 2010/1/18 João Mesquita <jmesquita@freeswitch.org>
Paul, I am not sure I understood your question. Can you elaborate a little bit better? Also, the code you have right now is buggy and I am working at it as we speak.
Right now, settings are not correctly persisted for some reason. I was working on a patch posted on Jira because I didn't want code to move a lot further and make it harder to merge later on.
Please be patient since this is a very new project.
Also, if you want a more live conversation, you can join #fscomm @ freenode. I am always there.
Regards,
João Mesquita FSComm Developer
On Mon, Jan 18, 2010 at 12:34 AM, Paul Li <plite2012@gmail.com> wrote:
João, thank you very much. It is now working like a charm. One small typo is about a normal clearing, "Call with (5000) failed with reason NORMAL_CLEARING", which I believe should be "Call with (5000) ended with ...", as this is not an error.
I have one more question on how to tie a remote endpoint to the default IVR at Ext 5000. I used to use the originate command, such as
originate sofia/default/1008%192.168.4.151 5000
so that the remote endpoint will be bridged to the announcement at Ext 5000. How can I do this in FSComm?
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
João, thank you again. It is working better. Do not bother my previous question. I have solved the issue regarding originate command call with no problem. I just need to adapt my thinking with FreeSwitch embedded vs standalone. I did find a bug related to SIP accounts. I have two SIP service providers, and one need a a custom parameter. However, the custom parameter also show up in the second SIP account's advanced tab (for custom parameter). I checked the registry and find the second provider does not have the custom parameter. So, the bug may be just a GUI thing, which you might forget to clear up. Is the first provider assumed to be the default gateway?
Inline... João Mesquita FSComm Developer On Mon, Jan 18, 2010 at 6:16 PM, Paul Li <plite2012@gmail.com> wrote:
João, thank you again. It is working better. Do not bother my previous question. I have solved the issue regarding originate command call with no problem. I just need to adapt my thinking with FreeSwitch embedded vs standalone.
I did find a bug related to SIP accounts. I have two SIP service providers, and one need a a custom parameter. However, the custom parameter also show up in the second SIP account's advanced tab (for custom parameter). I checked the registry and find the second provider does not have the custom parameter. So, the bug may be just a GUI thing, which you might forget to clear up.
Yeah, I will fix that bug tonight.
Is the first provider assumed to be the default gateway?
Right now, yes, but I am going to let you select tonight using the right click mouse button on the account list on the bottom left corner of the main window.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Just an idea: mark each gateway with a digit so people can chose gateway by prefix with #1 #2 etc. And, better to make the digit setable so one may like #gw1.....
Is the first provider assumed to be the default gateway?
Right now, yes, but I am going to let you select tonight using the right click mouse button on the account list on the bottom left corner of the main window.
Ok, time to update and try again. Paul, the custom parameters bug is now fixed. Seven, take a look how it is now. I think that it might fit most of the users needs since we are able to assign shortcuts to actions (ALT+NUM for instance). Remember, right click on the account row on the Accounts table and check the new context menu. I will keep refactoring the code to add more features. FSComm is getting big so some organization is needed. Regards, João Mesquita FSComm Developer On Tue, Jan 19, 2010 at 12:12 AM, Seven Du <dujinfang@gmail.com> wrote:
Just an idea:
mark each gateway with a digit so people can chose gateway by prefix with #1 #2 etc. And, better to make the digit setable so one may like #gw1.....
Is the first provider assumed to be the default gateway?
Right now, yes, but I am going to let you select tonight using the right click mouse button on the account list on the bottom left corner of the main window.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (3)
-
João Mesquita
-
Paul Li
-
Seven Du