hi sir, thanks a lot for quick reply. now i have been connected with own sip ip & call to GSM phone no. using our dialing pattern.
i want to read your softphone document & feature. In my company Sr. manager want to read your source code & functionality.so please suggest me ... 1- how to download your source code from internet? 2-how to compile source code for window OS as xp2? 3-which IDE/Framework we are using for working on your source code? thanks in advance! Regards, satish On Tue, Oct 19, 2010 at 5:30 PM, <ekiga-devel-list-requ...@gnome.org> wrote: > Send ekiga-devel-list mailing list submissions to > ekiga-devel-list@gnome.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.gnome.org/mailman/listinfo/ekiga-devel-list > or, via email, send a message with subject or body 'help' to > ekiga-devel-list-requ...@gnome.org > > You can reach the person managing the list at > ekiga-devel-list-ow...@gnome.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ekiga-devel-list digest..." > > > Today's Topics: > > 1. Re: how to use Ekiga softphone for calling....... (Eugen Dedu) > 2. Cleaning our config.h's situation (Julien Puydt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 18 Oct 2010 20:06:53 +0200 > From: Eugen Dedu <eugen.d...@pu-pm.univ-fcomte.fr> > To: Ekiga development mailing list <ekiga-devel-list@gnome.org> > Subject: Re: [Ekiga-devel-list] how to use Ekiga softphone for > calling....... > Message-ID: <4cbc8cbd.4030...@pu-pm.univ-fcomte.fr> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 15/10/10 11:45, satish gupta wrote: > > Hi Ekiga team, > > > > i want to used Ekiga Softphone for calling. i have download Ekiga.exe > from > > your site& install. > > i am facing so many problem for using this softphone. > > > > 1- how to register with our own sip ip in Ekiga softphone? > > You need to add/create in ekiga a SIP account using the information > given to you by your provider. > > > 2- how to call any GSM mobile no. like 9999994785? > > I think you need to write your phone number to URL bar and choose the > completion proposed. > > -- > Eugen > > > ------------------------------ > > Message: 2 > Date: Mon, 18 Oct 2010 17:23:48 +0200 > From: Julien Puydt <jpu...@free.fr> > To: Ekiga development mailing list <ekiga-devel-list@gnome.org> > Subject: [Ekiga-devel-list] Cleaning our config.h's situation > Message-ID: <4cbc6684.5050...@free.fr> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi, > > Problems : > (1) we don't include config.h everywhere, which limits its usefulness; > (2) we don't seem to have a 100% clear policy of where we should include > it from : it is for example included in both ekiga.h and ekiga.cpp, > while other places include it from their .cpp directly; > (3) the configure.ac does things about gtk-debug which should probably > belong to the "DEBUG support" section ; and it does things poorly by > putting directly things with -D in the flags -- it probably should do > some AC_DEFINE magic so it appears in config.h (which brings us to point > (1)). > > Solutions : > (1) remove and add #include "config.h" according to point (2) below ; > (2) fix a policy ; I propose to choose from two of them : > (i) include in all header files, as first non-comment and non-empty > line ; > (ii) include in all source files, as first non-comment and non-empty > line. > (3) modify the order and use AC_DEFINE instead of flags voodoo in > configure.ac. > > I would push for policy (i) for two reasons : > - if for some reason we would like config.h to have an effect on header > files, then it should appear there ; > - sometimes the header is the implementation! > > Comments welcome, help even more so! > > Snark > > PS: The commands : > find . -name "*.c*" -exec grep \{\} -e "^#include \"config.h\"" -l \; > find . -name "*.h" -exec grep \{\} -e "^#include \"config.h\"" -l \; > > will be pretty useful to find the files which currently do include, to > check if they either shouldn't or should sooner; and the same commands > with a '-v' added to grep's switches will later allow spotting the files > which should do the #include but don't. > > > ------------------------------ > > _______________________________________________ > ekiga-devel-list mailing list > ekiga-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-devel-list > > End of ekiga-devel-list Digest, Vol 51, Issue 11 > ************************************************ >
_______________________________________________ ekiga-devel-list mailing list ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
