Jump to content

nchtj

Members
  • Content Count

    958
  • Joined

  • Last visited

Everything posted by nchtj

  1. nchtj

    IVM FINALLy working

    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.
  2. 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
  3. 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
  4. 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.
  5. nchtj

    IVM and CAHTA

    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.
  6. 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).
  7. 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.
  8. nchtj

    IVM and TELCTAUSB4

    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.
  9. nchtj

    mailbox

    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
  10. nchtj

    axon axcrypt 1.6.4.4

    Axcrypt is open source file encryption software, it has nothing to do with Axon therefore we cannot support it.
  11. 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 alrea
  12. 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)'
  13. 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)
  14. 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) r
  15. 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.
  16. yes thats correct, a blank outbound server is the equivalent of specifying the 'use the default server' option. if you can register initially but not after a while, its probably a NAT/firewall issue - it just means that Axon is sending out register requests to the server but its not getting anything back. one option is to enable port forwarding to the Axon machine for UDP port 5060 , see if that makes any difference.
  17. for post #5 - are you sure Axon is listening on 5060 ? Can you see the logs saying anything in response to the phone's register attempt ?
  18. good to hear its working better ! your 3102 guide is very nice too ! i do need to clarify/correct a couple of things though: >> As your tutorial setup shows, the Axon External Line (FXO Line) is setup with the user ID as "user" and a blank password the tutorial doesn't say to make the password blank, it says to make the *server* blank. Step 2 of the NCH guide clarifies this. >> For example, the IP address in the Axon External Line "Server" name should be 192.168.1.124:5072 if the FXO (PSTN LINE) SIP port is set to 5072 if you keep the server blank in Axon you won't
  19. yea at this stage i have not got the caller ID thing sussed out yet, I can't figure out how to get the sipura to forward the ID information. but other than that its working nicely for me. but yeah like i said i'm going to update the guide, and if you feel it is ok i will incorporate elements of your guide into the NCH guide. who knows, i may find i went through some steps that i thought were obvious but weren't obvious to anyone else, which is why a lot of people are having problems.
  20. you can buy a sipura 3000/3102 box to connect your pstn phone to axon and then you can connect to skype through uplink and make calls that way. dont use a voice modem, they are unreliable. see: http://www.nch.com.au/hardware/fxo.html and see: http://www.nch.com.au/kb/10034.html
  21. while the sip protocol asks for contact ports, the reality is that the majority of voip providers / other vendors don't honour that and just send to the source port instead. the rationale is that whatever software / hardware has sent the packet is going to keep that source port open and will keep a mapping of that port active in its routing table so it knows how to handle any responses. based on our testing this principle works very well. if we relied on sending to the contact port instead, the reality is that many services would simply fail due to NAT routing / firewall issues. having sai
  22. one undocumented issue of the spa3102 (that makes it different from the spa3000) is that the sip ports used for the FXO and FXS *MUST* be different or else your FXO port simply will not work. by default those sip ports in the configuration are at 5060 which, if left untouched, will leave your FXO in a 'not working' state. change one of the FXO/FXS ports to 5061 and that should do the trick. on the spa3000 you can leave both those values at 5060 and it will work, the spa3102 will not let you get away with doing that. i had the exact same issue as you and it took me forever to work th
  23. the nch guide needs an update, we're addressing that currently. your guide is quite good, however your methodology is not the way we intended - while it does work of course, our idea is just a little simpler and is summarised like so: (this is very brief) - create an external line in axon with a nominated username/password and blank server field, set it to ring on a nominated group - enter those username/password details into the sipura's PSTN section User ID and Password fields - set the FXO dialing plan to forward to the line you configured in axon - [username]@[axon ip address] -
  24. we don't support that format sorry.
  25. hi, you seem to have the wrong product, and in fact you have the wrong company. We do not deal in graphics formats, we are an audio company. I have no idea how you converted png to jpg using Switch since I made the software and I definitely put no such feature in there.
×
×
  • Create New...