I am sharing the same problem as niksrulz. I enter information, exactly as guided in this: http://www.exetel.com.au/files/softphone.pdf
, however every time I dial a number, it fails. I've done plenty of fiddling (including the preceding advice), and nothing seems to work, though I have identified a few things that could be behind the problem.
1) Insufficient settings
The Exetel email gives information such as SIP server and port, yet the guide does not require us to enter such information. Are there any other settings we should be inputting, other than the five that niksrulz mentioned? A guide for a different service (http://www.freedigits.com/kb_configurat ... #x-lite3.0
) suggests something needs to be changed on the topology page. Is this the case with Exetel? Currently it is set to 'Discover Server'.
2) Wrong input
In the Exetel email, you are given a telephone number, yet the guide tells you to enter your 'SIP number'. I assume they are the same thing, but if not, this could be causing the problem
3) Wrong version
Hornet48, judging by that screenshot, it would appear you were using version 2.0. This seems to have a significantly different protocol for inputing settings (see the freedigits guide above). Version 3.0 is appearently based around a commercial product and has features ommited. This could be causing the problem. Similarly there is a demo version floating around that only allows PC-2-PC, but I don't think we have that. Perhaps version 2.0 is most suitable, and if so, it would be great if the exe file could be made available.
4) Not logged in
In the 3.0 user guide (http://www.xten.com/docs/X-Lite3.0_UserGuide.pdf
) it states that you need some sort of account and "You must always log into this service in order to use the phone, even if you do not want to use your CounterPath X-Lite account.". Well I can't see anywhere where I'm supposed to log in, so this could be the problem
5) Number input
When you dial a number, do you need to add anything to it, such as country codes etc?
There's also a possibility that our firewalls aren't letting it through. Is there any easy way to check this.
As you can see, there are so many things that could be to blame! I hope I've outlined them clearly. Does anyone know which might be the culprit? Any help would be greatly appreciated.