nchtj

There is a new version in testing, please contact tech support for further assistance. In IVM just go to the Help menu -> Technical Support page and the link is at the bottom of the webpage.

The reason for this behaviour comes down to the changes that Microsoft introduced for Windows Vista. Put simply, even if you are running under an admin account, you by default do *not* have admin access to the software. This is the new change that Microsoft have introduced with the UAC security feature. Since this is a Microsoft addition, it applies to all software across the board. This means that, if you want to change the startup options for the software, you have to exit it and then run it again *explicitly as administrator*. So you can right-click on the program in the Start menu and select 'Run as Administrator' from the menu. This will elevate your privileges and give you full access to the software. Once you do this you can change the startup options as you please. Microsoft introduced UAC to address security loopholes introduced by the fact that everyone uses administrator accounts on Windows regardless of if they need it or not. This limits the ability of viruses/trojans to infect your machine by asking you to authenticate any action on your computer that makes changes to sensitive areas e.g. Program Files or Windows folders. Under XP you could have programs install themselves quietly in the background without you knowing, but under Vista with UAC you will always get a prompt when this behaviour occurs (giving you a chance to stop this sort of thing occurring). You should already be familiar with UAC if you have tried to install any application on your computer.

For all our service-based applications, the 'engine' of the product runs as a Windows service. This service therefore needs to have access to your LAN folder. By default the service runs under the 'SYSTEM' account which has *no* access to LAN folders. You have to go into the Options -> General tab and click on 'Service Settings' and change it to run under an account that has *default* access to the shares. By 'default' I mean that, if the username/password to access shares is different to the username/password for that local account, it will only work if you check the 'Reconnect on logon' option when mapping the network drive (or browsing the network neighbourhood). A simpler method is to make sure the local / network account details match. Or the LAN folder can have no authentication at all. Note that once you do this then you cannot run IVM as a service anymore because it no longer runs under the 'SYSTEM' account. But this is a Windows limitation, it is simply not possible to access network shares using the SYSTEM account and without logging in to the computer.

Uplink bridges all phone calls through Skype, so it can only do what Skype can do (what the Skype API can do at least). Given that you cannot multi-line a Skype client that means Uplink cannot do that either. You would need multiple computers and multiple Skype clients.

Please email tech support for this issue and they can assist you further. In IVM go to the Help menu -> Technical Support Page and then click the link right at the bottom of the webpage.

We've seen this issue with other modems, the problem comes down to the modem trying to connect the call before IVM has had a chance to pick it up. Then after IVM tries to pick it up, it gets ignored by the modem because it thinks the call is already connected. So then the call disconnects. If you wish to confirm this, please email tech support for more assistance (in IVM go to Help menu -> Technical Support Page and click the weblink at the bottom).

We have a solution now, please email tech support for this issue and they can assist you further. In IVM go to the Help menu -> Technical Support Page and then click the link right at the bottom of the webpage.

We have a solution now, please email tech support for this issue and they can assist you further. In IVM go to the Help menu -> Technical Support Page and then click the link right at the bottom of the webpage.

For all our service-based applications (such as IVM), the 'engine' of the product runs as a Windows service. This service therefore needs to have access to your LAN folder. By default the service runs under the 'SYSTEM' account which has *no* access to LAN folders. You have to go into the Settings -> General tab and click on 'Service Settings' and change it to run under an account that has *default* access to the shares. By 'default' I mean that, if the username/password to access shares is different to the username/password for that local account, it will only work if you check the 'Reconnect on logon' option when mapping the network drive. A simpler method is to make sure the local / network account details match. Or the LAN folder can have no authentication at all. Note that once you do this then you cannot run IVM as a service anymore because it no longer runs under the 'SYSTEM' account. But this is a Windows limitation, it is simply not possible to access network shares using the SYSTEM account and without logging in to the computer.

Axcrypt is open source file encryption software, it has nothing to do with Axon therefore we cannot support it.

We support RFC2833 and In-band, but not SIP Info. Codecs supported are G.711u/a, G.726 and GSM. G.729 is not supported because it is a royalty-based codec. If key responses aren't working then (assuming RFC2833 is being used), it's a 1-way audio issue. You can check this by enabling the SIP logging in properties for your SIP line in IVM (Advanced tab) and checking the logs to confirm this. Port forwarding will only make an effect on the software if the software's networking wizard failed to find your external/public IP address when you installed or ran it. Since the software will already make use of either uPnP or STUN to resolve networking issues, running port forwarding at the same time may make the behaviour less predictable. So you should only run one or the other, but not both. If you want to keep port forwarding then you should enable the static IP option in the Networking tab of the SIP line properties. If you do this, also remember to keep the Local SIP/RTP and External SIP/RTP ports the same, or else you will get further problems (all these are also configurable in the Networking tab). For audio issues we recommend you maintain talks with your VoIP provider in this circumstance because their gateway does a lot of the audio processing and they will normally have some good advice to offer in this area. Some providers say that they primarily support G.729 as a native standard and they have to transcode to other formats when necessary - this is one area where audio degradation can occur. Since G.711 is the only mandatory codec under the SIP standard, a good VoIP provider will support it natively on their gateway. Your own Internet bandwidth is the other area where audio issues can occur. We support QoS by default in our software so check to see if your router supports it. Also make note of *both* your upload *and* download bandwidth, as VoIP requires both directions equally. G.711 for example needs up to 64kbps downstream and upstream equally. GSM needs only 8kbps, while G.726 needs 32kbps. If the stream of audio up/down through your router doesn't occur at the same sorts of speeds then this is another big area where audio degradation can occur. You can also try a benchmark test of connecting the computer directly into the modem and see if the behaviour is any different (i.e. bypass the router).

did you check the option in the advanced external line settings for that voip line that says 'Disable call activity polling (only use if call breaks after 60 seconds)'

we use engin as our primary voip service at the NCH office (use it in Axon i mean) and its working very well for us. did you get the server address correct ? byo.engin.com.au ? codecs have nothing to do with the ability to register a service. why are you using carousel as well ? is it just because you couldn't get it to work in axon or are you also planning to connect real telephone lines into axon too ? if your serious about taking our products to your customer base, note that we offer reseller services for customers just like yourself (http://www.nch.com.au/reseller/index.html)

the fundamental issue here isn't about registration times, its networking. what many don't realise is that we honour the registration expiry times returned by the VoIP server, so whatever frequency Axon is using that is what your VoIP service is asking it to do. so when people are asking 'how do i change the registration expiry time?', the real question should be 'how do i keep my NAT/router ports open in order to receive registration responses and call requests from the outside world?' the answers can get complex (just like networking as a whole), but the suggested ideas are: 1) run the axon networking wizard and see what it says - it will try the uPnP and STUN lookup options and see if any of them work. if STUN doesn't work it means you have a symmetric router which is the most difficult type to have, and you will have to setup port forwarding on your router (see next option) 2) port forward all responses coming in to port 5060 on your router to the Axon machine. this will mean that you don't have to worry about router ports closing and any incoming call/registration requests getting blocked. also you can try port forwarding on 8000-8020 in case axon has to relay audio through its machine, but only do it if you are experiencing audio issues - if you aren't then don't worry about it (sometimes it causes extra problems). contact me at tj [at] altoedge.com for a test version of the next axon too, i would very much appreciate someone like yourself (an active member in the community) to test out new versions and give feedback on how things are working on your system/networking setup.

the new spa3102 guide isnt up on our site yet, thats still the old spa3000 one. i'm still trying to write the spa3102 one and am still going because the new unit we just got (and some customers have got too) doesn't seem to want to work right. so now i need to figure out whats wrong before i can publish the guide.