pythonpoole

Dual IP Address not working - I'm going to have to assume this is a bug in Axon then. You'll have to report the bug to NCH directly or put it in the suggestions topic. This is unlikely to be fixed soon though. One Way Audio - I still have to think about this one. I'm not used to working with such complex networks. They tend to have so many variables that it's hard to pin-point where a problem lies. Just a note, I think you will need to forward ports for each PC running the softphone. The softphone needs to connect directly to the VoIP provider for the call and I find I get much better performance out of ET when I forward the port directly to the computer which is running the ET software at that port. I'm not sure forwarding everything to the Axon server is going to helping much. Extensions not ringing - I don't know what to suggest, this seems very strange to me. Does the other end report any error code (e.g. Busy, no response, etc.)? If you can, try and post the SIP trace log of the call (from both ends if applicable). On-Hold not working - Just make sure Express Talk is set to "Link to IMS On-Hold Player (Professional Option)".. other than that, there is no other option to try and force ET to use IMS over the VoIP service's MOH. Nor is there an option in either ET or Axon to disable signalling of MOH to the VoIP server. This leaves you with 5 options: 1) Contact NCH about the issue, see if they can help you (will take a while for response, no guarantees) 2) Use the NCH development service and request the feature to allow disabling of MOH signalling to the VoIP provider. They will charge you to program the custom feature, but they will probably also give you a large discount if you let them use the feature in the next public release of Axon/ET 3) See if your VoIP provider can disable their MOH system for your account 4) Switch VoIP providers 5) Live with it the way it is Curiosity : High CPU Usage - This is very abnormal, and I don't know what would cause this. For me axon uses "0%" processor usage (according to task manager; using a P4 2.4 GHz processor) when idle, and not much more when active.

I'm not sure about your caller-id problem. I've had a similar problem using another FXO adapter (the Sipura 3000 adaptor). I was never able to get the Caller-ID passed on to Axon. I don't know if this is a limitation of using FXO devices in general, or if it is some sort of incompatibility between the FXO adaptors and the Axon virtual PBX. As for the transfer problem, if you've tried both a confirmed and blind transfer using the method specified in the manual and neither worked... then the last thing I can suggest is to try and initiate a transfer directly to Axon by doing a flash hook followed by a second of silence, followed by the number you want to dial. Then try hanging up once the other party answers. I have no idea if this will work, but in IVM the default transfer dial string is !, (meaning flash-hook, followed by a pause, followed by the number to dial) so it may work with a phone connected to Axon as well. One last thing to note: Not all VoIP providers will allow call transfers. If there is only one communication channel permitted, call transfers will fail. In addition to this, some VoIP services do not allow or are not compatible with Axon transfer requests regardless of the number of channels available.

Dual IP Address not working - Have you tried enabling only the manual configuration (i.e. disabling UPNP and Stun)? This should force Axon to use the IP of your choosing. One Way Audio - To my knowledge the only (or at least major) cause of this problem is blocked ports on the router's firewall. I have no experience with IPSec, so I don't know exactly what it does, but if there was truly no firewall and you ran the network set-up wizard in the softphone, there shouldn't be any one-way/no-way audio problems. - If your router has a DMZ option, try enabling it for one of your voip phones/softphones, this should truly disable any firewall and open up all ports for communication for the specified device. If there is still no audio after using DMZ, then there is something else causing the problem. (Also note there are usually several firewalls (both hardware and software based) in a typical network set-up, and each firewall will have to be modified to allow communication on the necessary ports to ensure two-way audio. - If DMZ does work, then the issue is firewall related and you will need to determine how to forward specific ports on the router's firewall (as well as any other firewalls which may exist in between the Internet connection and the server/voip phones. Extensions not ringing - Make sure the extension is registered properly with Axon when the call takes place (Axon will report the IP address of the extension in the web config panel if it is registered) - Make sure there are no errors displayed on either side (Axon or the softphone) which may indicate a problem - Be sure to run the network set-up wizard on the softphone (assuming it's Express Talk) to fix and diagnose any network communication problems On-Hold not working - This is because the softphone will send a 'on hold' signal to the server end (e.g. Axon) to let the server know the call is on hold. If the server doesn't respond, the softphone (Express Talk) plays a simple chimes tune. If the server does respond, the call will then play the MOH (music on hold) provided by the server. Unfortunately what I think happens is Express Talk connects directly to the VoIP provider when in a call, so Express Talk is actually sending the signal to initiate MOH to your VoIP provider rather than using VRS. - In some cases this is desired. For example, sometimes I use Express Talk with a remotely hosted PBX system (running Asterisk) which offers its own MOH system. When I put a caller on hold, I want and expect Express Talk to use the MOH from the Asterisk Server. Express Talk performs this task correctly, and for that I am pleased. But it is also undesirable in a case like yours where your VoIP provider offers its own MOH (not very common) and you wish to use IMS instead. Cannot use DNS Name on Extensions - I'm not exactly sure what the problem is? You should be able to enter an IP address or hostname/DNS name of the server, and I'm pretty sure appending the port number to that (e.g. mydomain.com:5071) should work. What exactly is it you are trying to accomplish, and how is it not working?

Have you taken a look at the Express Talk SDK? It will help you control many functions of the softphone remotely (e.g. initiate calls, answer calls, put them on/off hold, dial digits, show/hide the interface, etc.) I don't know what the Unified API Java Demo is, but I find it unlikely it's compatible with Express Talk.

Indeed this is a port forwarding issue. Your firewall appears to be blocking the ports Axon and the Softphone are using to communicate. This is normal, however must be corrected for two way communication to be successful. Please reference your router's manual to determine how to forward (unblock) ports, and then set the router up to forward the ports you have chosen Axon/the soft phone to use. Also be sure to run the network set-up wizard in the Softphone.

Copied Directly from the manual of the Grandstream ATA For future reference, the method of transferring the call is usually dependent on the phone hardware you are using with Axon. The manufacturer will decide on a method for transferring calls (possibly unique to their system) and will then send on the transfer request to Axon using a standard protocol.

What software are you using? I don't think there is a 'universal' SIP account manager software, it would be dependent on what PBX system you're running (e.g. Axon, Asterisk, 3CX, etc.) Axon has a built-in web server so it can be controlled locally or remotely through an easy to use web interface. The interface allows control of all aspects of PBX from account management, to dial plans, to call routing, logs, and more. Here are a couple of a screenshots:

1) Carousel is only compatible with a select number of professional telephony boards. You will probably have to check with NCH to be sure, but I doubt your current modem is compatible. 2) Yes, that is the correct product. The SPA3000 and 3102 go for around the same price despite the fact the 3102 has a built-in broadband router (about the only major difference). They typically sell for anywhere between $80 - $100 new depending on where you get them from. Note that most big retail stores (e.g. Target/Walmart/Best Buy) probably won't carry the item. These retail stores tend to sell consumer products that are easy to use and configure for the average person. This product is more for advanced users, experts and businesses who have a good idea of what they're doing and exactly what they need the product for. You're more likely to find these products in lesser known computer stores (the type where the service isn't that great, and you're expected to know what you want), and online stores. Take a look here for a bunch of online stores (which may also have retail stores in your area) that sell the 3000/3102: http://www.google.com/products?q=SPA3000+O...=1&ie=UTF-8 Just a word of caution before you buy: I won't lie, it is not simple and easy to get working and there is no wizard or guide that comes with the product that will help you out either. That being said both NCH and myself have written step-by-step guides for setting up these adaptors. As long as you follow the instructions, it should be relatively straight forward to get working. 3) Using Uplink incoming calls from Skype can be routed to Axon just as if the call came in from your regular phone line. Also outgoing calls can be put through on Skype to save money, although I recommend using another VoIP service for outgoing calls rather than Skype.

Yes you will require an FXO adaptor (such as the linksys/sipura 3000 or 3102) to convert the analogue line into a digital VoIP line. You will no longer require the use of the modem after that, as the FXO adaptor acts somewhat like a modem (as an interface between the PC and phone line).

You are probably looking for a combination of IVM and Axon. IVM will handle incoming calls and answer them automatically, prompting the caller to choose options from a menu. It will also take care of voice mail and whatnot. Axon will handle all the call routing for your business, sending the caller to the appropriate phone extension(s) or holding them in queue until someone is able to answer the call. It also connects to external VoIP lines. Internally, each phone extension would be connected to Axon. This allows calls internally between extensions, and also allow for incoming/outgoing call from/to external parties. Note that Axon is only compatible with VoIP telephone lines. If you wish to use traditional analogue lines, you'll need to purchase an FXO adaptor, or use NCH's carousel software in conjunction with a compatible telephony board.

I don't think this is a problem with Axon, it's probably an issue with the phones. Some IP phones have a gain setting for volume in and out. What might be happening is the volume out gain is low so when calls are made to customers they can't hear you. For internal calls it could be a case of the call comes in soft and the phone automatically boosts the volume with gain-in control, so you don't notice. It could also be a problem on the VoIP provider end of things. This would also explain why internal calls seem unaffected, but calls to external parties have the problem. To confirm this, try calling out from one of your phones to your business number and then answer with another one of your phones (thus making sure the call is sent out externally and then back in), see if the volume is soft. If so, it is definitely a problem with the VoIP provider, if not I think it's the phones.

Hmm, I'm not sure what the problem is. Is the OGM called exactly "PlayIntroduction"? Is it in the main/root directory (i.e. not in a sub folder)?

The string/code should be independent of whether you transfer to mobiles or land lines. It will be different based on the phone provider you use. I know that the default ( !, ) works in many cases, and with most PBX systems.. but in other cases (such as the Vonage phone service) it fails. I'm not sure how you determine the correct transfer code for your telco provider, that you might have to ask them (the provider) or wait here for someone else to respond. Edit: Converting to digital is not necessary, although if you converted the lines to VoIP using an FXO adaptor, you could transfer calls using a VoIP provider. This would not only be cheaper (call cost wise), but would solve the problem with not knowing the string code. The only disadvantage is setting up an FXO adaptor is a bit complicated and if you aren't experienced in that area it may be somewhat difficult to get your head around.

I don't think there are any plans to add G723 or G729 support in the near future. Part of the problem has to do with their proprietary nature meaning a license has to be purchased for every user with the software or hardware that can support the codec. For example a license for G729 support is about $10. This would make it impossible to giveaway to users for free in software like (the free versions of) Express Talk and Axon, and it would likely cause the price of NCH's VoIP software to go up to compensate for the cost of the codec licensing.

I've put my MSN address in my user profile.

Well I guess it's for real then. I'm a bit disappointed, but oh well. I kind of expected it anyway... it's not the first time NCH has released a product for free and then start charging for it. I can't blame them though, the software is still good quality and no one can argue with the price (it used to be).. but I think it's ridiculous to suddenly bump up the price of a free product to $100 in one day with no real difference in the software.

We'll have to wait and see, as far as I can tell this "Axon Plus" version is brand new (as in today), and if anything it could be an April Fools joke. The download doesn't seem to work, and the purchase page doesn't allow you to buy/select a quantity for Axon Plus licenses. Anyway, I hope it is a joke because one of the best reasons to use Axon is the fact that it has always been a free product. I also think a big chunk of the revenue from Telephony products comes from users who download Axon, think it's cool and decide to purchase the add-on software packages like IVM, VRS, IMS and Quorum. By making Axon a paid product, I think it will discourage users from using it (instead of free alternatives like Asterisk), and NCH will probably lose out on potential sales that would have come from free Axon users.

There is no way for a user to delete his/her own account. I suggest you just leave it be if you're not using it anymore and perhaps a mod will delete it for you. I don't think you should be concerned over this.

My guide is located here: http://nch.invisionzone.com/index.php?showtopic=5091 NCH's guide is here: http://www.nch.com.au/hardware/setup/fxo.html

Firstly (concerning the hyphens), Express Talk will basically send whatever you put in the textbox on to the VoIP provider (including the hyphens), so if the VoIP provider is not set-up to handle/ignore the dashes that explains why the call isn't going through (I am going to assume x-lite automatically removes any dashes or brackets before sending the call through). As for the audio problem, be sure to run the Network Setup Wizard (under options -> network) and if you haven't done so already, it is a good idea to forward the ports on your router that are being used by Express Talk otherwise this may be blocking the audio from coming / going.

Yes, that is the right device, and you are correct, having the SPA3102 should not disrupt your current router's operation. Now I will be honest here, hooking the SPA3102 up to Axon is a bit tricky. Having said that I have written a step by step guide to set it up and so has NCH, so just so long as you follow it correctly, you shouldn't have much of a problem (hopefully).

I think this must be a bug in the software that nobody has noticed until now. You might be able to correct the problem by deleting the relevant keys in the Windows registry.. other than that, I think you'll have to contact NCH directly about this one.

Have you set-up Express talk with a VoIP service? If yes, are you sure the service you signed up for allows calls to the number you are dialling? For example, if you don't have a paid account, it is unlikely the VoIP service will allow you to dial PSTN lines (i.e. regular phone numbers) for free thus resulting in "Declined." If you are sure the service should allow calls to the number you are dialling, then it is also possible you are dialling the number incorrectly. For example, some VoIP services require you put in the area code (even for local numbers that normally don't require it), other services sometimes require the country code be prepended to all calls.

I never received your PM, but here are some links: AltoEdge: http://www.nch.com.au/hardware/fxo.html Ebay: http://search.ebay.com.au/search/search.dl...op=1%26fsoo%3D1 In AU or ships to AU: https://www.warcom.com.au/shop/flypage/Networking/Voip/1505 https://www.mynetfone.com.au/shop/voip-devi...inksys-spa3102/ Not sure about AU shipping: Voip Store: http://www.888voipstore.com/linksys-spa-3102-pr-16377.html Voip Link: http://www.voiplink.com/Linksys_SPA_3102_p...ys-spa-3102.htm Note: The only difference between the 3000 and 3102 is that the former doesn't have a built-in cable/dsl router.. so assuming you have a router already you only need the 3000.

I know that is what you want, and that is what the 3102 adapter does (note that Linksys/Sipura makes many versions of these adaptors that look exactly the same, but perform entirely different functions). Also note that the 3102 also does voip to phone line (and at the same time, phone line to voip), so it is still possible your friend has the same model and is simply not using the phone line to voip feature. However most providers give out PAP/PAP2/PAP2T adaptors (including Faktortel I think) which are practically identical in looks to the SPA3102 and the SPA3000 (I have both the 3000 and PAP2T and the difference in size is negligible and even the labels do not clearly distinguish them).