OK, someone earlier today suggested the FSClient sip softphone. Maybe I'm just totally stupid, but this is not working in the least hardly! I've managed to make an inbound call to my extension, and answer the call with FSClient, but I can't hear any audio from the line I used to call my extension with which is registerred through FSClient. The weird thing is, I have a blue Snowball microphone connected via USB to my system, and I can hear audio through my handset which I used to call the FSClient line just fine. So my mike is working no problem. If I make an outbound call however by dialing 1 then the 10 digit number I'm calling, as required by my sip provider, which by the way, is CallCentric, then the line I dial never rings, and of corse, through FSClient, I hear absolutely nothing. I've gone to the calls list of the program, hit shift+F10 for the right click, on the active call, then went to: "Their volume," and the star was on 0. I increased it all the way to the max of 5. It did no good at all. I went into options, and hear's where the accessibility part comes in which makes utterly no sense! I can set the main input, and the speaker phone input both just fine, and when I hit save, they stick. However, unless I select primary sound driver from the main output, and from the speaker phone output, and the ring on combo box, they don't take. If I set those outputs to my Creative SB Audigy II ZS sound card, then hit save, it doesn't take. If I hit save after selecting my SB Audigy, then go back into options again, I see the inputs still are set properly, and still work like a dream, but the outputs don't do anything. When I look at the combo boxes, nothing is selected. Again, the only way around this is to go to primary sound driver, but even if I do that, and even though it then sticks, there's no sound at all from the output of the application. This isn't a problemn with my sip provider, as if I use Bria on my IPhone, or CSip Simple on my Android device, it works flawlessly both directions. It's definitely not a firewall or network/nat issue either, as if that was the case, I'd not be getting audio out of the client either, which of corse again, I am. I really am fully convinced it has to do with the output combo boxes being really buggy and not hardly ever sticking. I've not only uninstalled, but have totally revoed the app, and reinstalled from complete scratch about 3 or 4 times now, and each time, I get identically the same results. I've further tried this on about 3 different computers. One on XP SP3, one on Windows 7 Home Premium 64 Bit, and one on Windows 8.1 64 bit. Yes, I know in the documentation by the way when making an outgoing call, it says to start with the hash/pound symbol, then the number, then the account number 1-9. Obviously I only have one account set up, and I configured it on 1, so a number then in the US may look like: #121255512121. That won't work either. I've tried dialing, then hitting enter to send the call, and I've also typed the number then tabbed to the answer button, and hit the space bar.
Nothing! Zilch! Yeah I'm registerred, as how else would I be able to get incoming calls? OK, there is no instream audio, only outstream, but still! So, yeah, right now, unless you all have some hints which maybe a stupid man isn't catching, I'm sorry, but this client is *not!* gonna work for me! It seems massively! buggy at first glance. Chris. _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
