pythonpoole

Is there more information in the log (there should be for example a received packet from Teliax, if not.. it looks like they're completely ignoring your register attempt for some reason.. or sometimes it happens because the VoIP service is not running, or the server is not reachable (possibly because of a port forwarding issue). I'm not an expert in this field (i.e. sip traces, etc.), so I hope others on these forums will help solve the problem since I'm really not sure why the server isn't responding.

Well if you already have the OGM programmed to take credit card payments, then you should be good to go and ready for testing within the hour. IVM can hook up directly with your VoIP account and start receiving calls as soon as you need them. If you don't have the OGM programmed already.. this is not going to be an easy task, and even if you had a large team of programmers.. I would not recommend you try to develop a credit card payment system, test it, and then deploy it in just a couple of days. This goes for any major system, but IVM is simple enough that if you have the OGM ready it'll only take a few minutes to get setup. The OGM (if it isn't programmed) will require that you ask customers for a credit card, take the input, store it to a variable which then executes an external program/plugin (that you will need to develop) that checks the credit card input to see if it is a valid number. Then you should either have the program interface with a credit card payment system directly (if you have one), so customers are charged automatically, or more likely store the credit card data in a database (using the database interface plugin) so someone can manually check it later and then charge the credit cards as needed). The phones that can access your IVM system is entirely dependent on your VoIP provider. Most providers (assuming you have purchased an inbound phone number (DID) or a calling plan that includes an inbound number then anyone who calls the number whether it be from a land-line, mobile phone, or VoIP phone shouldn't have a problem using the IVR menu and OGM you've setup in IVM. Note that only touch-tone enabled phones (i.e. not pulse or rotary dialing phones) will be able to input digits into the phone system (as with any IVR system out there). VoIP service providers usually will have your service setup instantly, although it is always a good idea to check their FAQ or similar just to make sure this is the case if time is such an importance. A service that I use and find works well is Voice Network ( http://www.voicenetwork.ca ). They provide toll-free 1-800 numbers to anyone in the US/Canada for $1 month plus 4c/min (this is one of the best deals I've seen). They also offer other inbound numbers across the US (see http://www.voicenetwork.ca/usa_did.html ) - if you pick the pay-as-you-go plan, you can have up to 6 simultaneous calls, otherwise you will be limited to only two (on the flat rate / no per minute charge plan).

Strange. Are you sure the server is voip-co4.teliax.com? (Just because all the demo configurations and such on their website use voip.teliax.com) All the correct config details can be found in your Teliax control panel under support. If you are still having a problem, I suggest that you go to the 'logs' tab in Axon's web control panel and turn on SIP trace logs and then post your log here so we can perhaps try to identify the problem. Also, on another note.. make sure in your Teliax control panel that you only tick 'ulaw' and 'gsm' under the Codec settings (in account details).

The port doesn't matter. Just so long as it's open and forwarded on your router, it should work fine. The default for SIP communications in general is port 5060 I think, but your router (or even your internet service provider) may block this port, so you'll need to use an alternative one that is open. But yeah, it doesn't matter at all (in fact I have my Express Talk set to use SIP port 78 on this computer and it works fine. Let me know if you solved the audio problem after the port change.

It's very simple, 1) Log into your Axon web control panel 2) Click 'External Lines' 3) Click 'Add New External Line' 4) Set 'Line Name' to anything of your choice (just for your reference) 5) Set 'ID or Username' to your Teliax username, and password to your Teliax password 6) Then choose the extension or ring group incoming calls should go to 7) Select 'Use Gateway Server' and enter voip.teliax.com into the textbox 8) Save changes and you should be good to go Note: Incoming calls should start to work right away, outgoing calls require you to setup a dialing plan (like Asterisk) To setup a dialing plan, 1) Click 'Dialing Plans' in the Axon web control panel 2) Click the Edit icon on the default dialing plan 3) At the bottom of the page, set 'If none of the above applies, dial on line' to your Teliax line. If you want a more advanced dial plan you can come back later and add additional dialing rules (so for example you can call internal extensions.. the way it would be setup now is all calls our routed through to Teliax).

This is very common problem and usually occurs when your internet modem/router has not been properly configured to forward the necessary ports. Please see http://nch.invisionzone.com/index.php?showtopic=737 for common networking problems and solutions that should help fix the issue. Please also make sure you Run Network Setup Wizard in Express Talk (options>network) This is an automated wizard that will try and automatically setup Express Talk for the best possible connection based on available open ports, whether your router is NAT enabled and whether it supports UPnP etc.

I've been thinking about this a bit now.. and can only come up with one plausible solution.. and even then it is a work in progress, in fact I'm not even sure it would theoretically work because I'm inclined to think Axon would only log the actual number that was forwarded on to the External Line and not the dialed number. But assuming it did log the dialed number as well... When IVM answers on the 555 extension, it should execute a plug-in program (which you will need to get someone to develop for you) that will parse the current Axon log file and identify what the last dialed number is and then send it back to IVM as a variable which can be used to transfer the call at a later time. But now as I think about it more, I'm inclined to think that Axon won't log the dialed number, and this will be another failed attempt at a theoretical solution for this problem. But... there is still some (little) hope (read below). The other way (which could theoretically work, and is the only way I can see it working at this point) is to develop a completely separate application that acts like a very simple VoIP PBX (keep in mind this is no easy task). My logic is this: Have the 'overdue' dialling plan that will simply send all calls (without altering the number) to an External line called overdue for example. The external line 'overdue' will essentially be an SIP account you set-up with your custom basic PBX program. The only actual job that program will have is to transfer any calls that are made to it (through the overdue line) to IVM's 555 extension and set the caller id for that call as the number that was dialed to reach the program. As a result, incoming calls on IVM's 555 extension will have the CID of the number the customer was trying to dial and then you can simply use %cid% to transfer the call after the overdue message to the appropriate destination. It is complicated, will take time to develop, but theoretically is a plausible solution.

I answered your topic in the Axon forum ( http://nch.invisionzone.com/index.php?show...view=getnewpost )

Currently, there is no built-in billing system for Axon, so if you are willing to manually control a user's overdue status then here is my idea: - 1 - 1) Create a new dialling plan in Axon 2) Create a dialling rule in the plan that says if the number starts with 0, remove 50 digits (all), and prepend 555 and dial on line [Extension] 3) Do the same (create a new rule) for digits 1-9, * and # When someone's account is overdue, switch their dialling plan to the this one and all calls that they make will be re-directed to IVM's 555 extension. - 2 - It should be easy to set-up an OGM in IVM and have it play the overdue message. (When creating a new telephony device (SIP account in IVM) in the last tab of the line properties it will let you override the default OGM with another one of your choice for that line. - 3 - Now here's the problem, I can't see any way of transferring the number that was dialed on to IVM if you use this way (and at the moment I can't think of another way to solve this problem). So you would have to have an OGM for the customer to enter the number they wish to dial again, and then transfer them).

I don't have any personal experience with the device.. although here is some information that might be of some help: The last post in this topic shows how the person solved a similar problem (also with the Way2Call modem): http://nch.invisionzone.com/index.php?show...amp;hl=way2call Also here is a topic with someone who uses and highly recommends the Way2call modem for IVM and might be someone to ask if you still have any problems. http://nch.invisionzone.com/index.php?show...entry6996

Remember that in IVM you are asked to specify the "Number of simultaneous calls allowed" in the telephony line properties setting window for each telephony device you have. Make sure you have it set to at least 2 if you are expecting multiple incoming calls.

Yes, Express Talk can support up to 6 incoming phone calls at a time. However, the amount of incoming phone calls may be restricted by other factors (such as limits set by your VoIP provider). Often outbound calls are completely separate to inbound, and some providers will for example only give you 1 incoming channel/line but provide you with for example 3 outbound lines/channels. Many services are reluctant to give you several incoming channels especially if you're on a flat rate plan for the DID because they will get not benefits from allowing so many calls, in fact they may actually lose out from the costs of bandwidth and whatnot from those calls. Also, are you using Axon in between? Or are you connecting ET directly to the VoIP provider? Is the Voicemail system on your end (e.g. IVM)? Or is it going to the Voicemail system from your provider (this will help establish whether the provider is limiting the calls, or if the problem lies internally).

This sounds like a problem with re-registration. Some VoIP services think that you are trying to register two devices for the same account, will stop allowing calls to go through. On the other hand, if the program doesn't register often enough, the service may think it has just kind of gone over time, and will assume it's no longer there. My understanding is that NCH's software is supposed to re-regsiter as often as the service requests, but I knew I had the same exact problem with a service called FreeDigits (which is no longer in service, however still provides already registered users with the old service) that originally kept stop answering calls after a while, but if I closed and opened the program it would work again. After talking directly with the NCH development team, I was able to get the problem fixed for the next version of the software (which luckily was coming out in only a few days).

I will admit that the SPA3000/SPA3102 are sometimes tricky to configure and to get working right, and I will be honest that I have had difficulty setting them up in the past, but so far it is the only FXO device supported by NCH to work with their products. Theoretically having 4 SPA adapters should not be a problem, but I haven't tried using multiple devices. Also the Caller ID can work, NCH found that by adjusting the time before the call is answered, you can retrieve the CID information.

Since IVM doesn't actually have built-in scheduling for calls, you will need to set this up with another program, or with Microsoft Window's built-in scheduler. To use the Windows Scheduler, 1) Open the Control Panel 2) Double click on the icon for Scheduled Tasks (under Performance & Maintenance if you are in category mode) 3) Double click add scheduled task 4) Click Next 5) Select the IVM executable from Program Files\NCH Swift Sound\IVM\ 6) Do not worry about the rest of the settings you pick in the wizard, you will change them later (the basic wizard doesn't let you set up advanced schedules like repeat every 5 minutes) 7) Make sure you have the 'Open Advanced settings <blah>' (can't remember the exact wording) checkbox ticked on the last screen and then complete the wizard. 8) After the Advanced Schedule settings window is open, under the Schedule tab, make sure it is set to daily and for example 12:00 AM, scheduled for every day 9) Then click the Advanced... button 10) In the options window, tick the Repeat Task option and set it to every 5 minutes for example, and set "Until:" to the Time 11:55 PM. 11) Now go back to the Task tab, and in the Run: textbox, add the following to the end -outbound 18005551234 (obviously, replacing it with the number you want to to call). The textbox should now read something like "C:\Program Files\NCH Swift Sound\IVM\ivm.exe" -outbound 18005551234 You're done. Windows should now tell IVM to make an outbound call to the 1-800 number every 5 minutes every day using the OGM you have configured in IVM (i.e. to e-mail you if there is a problem).

As far as I know, all the Linksys and Cisco VoIP products are compatible with NCH's software. If you are trying to use an analog line with Axon (i.e. need an FXO adapter), I recommend (and so does NCH) using the Linksys Sipura 3000 or 3102 FXO/FXS device. I don't have any experience with Grandstream, so I cannot help you there.

Even though you will not actually hear the DTMF tones on your side when pressing the keypad buttons in Express Talk during a call, please be assured the DTMF signals are still being sent over on your VoIP line to the destination. It should act like any other telephone keypad in a call. If you are experiencing difficulties, it could be that for some reason your VoIP service is not receiving the dialed digits and relaying them on. One other thing to point out is that on digital VoIP networks, there are 3 main ways to send the DTMF tone signals: inband, sip info, and rfc2833. I believe (although could be very wrong) that NCH products only support inband DTMF signals, and hence the problem may be that your VoIP provider only accepts one of the others. Also, you cannot get a refund for the product once you have activated/used it. NCH offers trials and/or additional free versions of every product for you to try out before you buy. NCH suggests that you don't purchase until you are sure all parts of the software are functioning correctly with your setup.

It is also highly dependent on your location. For example, in Australia, when the phone is not in use, I believe the remote plays a continuous series of tones down the line (that isn't heard by the consumer), where as in North America the line goes pretty much dead (but still live in terms of voltage). When someone hangs up on you in Australia, you immediately get a busy like signal, where as in North America you either get a moment of dead silence or it returns you to a dialtone so you can make another call. On this page http://www.nch.com.au/hardware/setup/fxo.html, NCH has listed the proper disconnect/hang-up settings for Australia, (the defaults on the device are for North America) and you can probably find more configurations online.

Have you forwarded the required ports on your internet router? If you plan on using uPNP, are you sure your router supports this feature?

Well you should be able to use Axon. Just so long as you have a LAN, as you said, then the extensions should be able to connect to Axon via the internal LAN IP address of the computer with Axon.. and then Axon can use the broadband connection on the computer to connect to the external VoIP providers. Although you can only use one of the 256kbps connections with Axon.

I didn't realize sending the date and time was part of caller ID standard protocol. I would have thought the actual phone should keep track of when incoming calls come in. On the other hand I wouldn't really know and I haven't looked in-depth into how Caller ID is actually sent. What particular phone are you using?

IVM is designed to operate as almost a server application. Typically it runs on a dedicated computer and all other programs that need to use it (e.g. Express Talk) on different computers connect to it via the local area network. I wouldn't recommend having multiple installations of IVM on different computers for several reasons: - You would have to purchase new licenses for each computer you wanted to run it on (which will get quite costly) - Maintenance of the system will be much more difficult, and if you need to change how one program operates, then you'd need to go to each one individually and change it (although IVM has some sort of auto-update feature that looks for new config files in a network location, I've heard it is a bit buggy but personally haven't tested it) - The cost of having several high performance computers available to basically just run IVM wouldn't be feasible, and if you did use them for other uses (such as web browsing) you risk causing quality loss and/or disruptions to any phone conversations. Also my other concern is when you say each computer gets an individual 256kbps line... usually what happens is a business will have one 256 kbps line and they use an intelligent switch which can split the internet connection up for several computers without seeming as though there is any lost bandwidth. When it comes down to technicalities, no matter how fast the switch can "switch" you can't make bandwidth from nothing, and it'd be impossible to guarantee each computer 256kbps of bandwidth. If your business truly has for example 10 completely standalone internet connections for each computer (which frankly I cannot see happening, I've certainly not heard of businesses doing this, and it'd be much cheaper and easier if the computers were all on a shared LAN network and could access one internet connection. But anyway, assuming this is the case, you will have problems getting all your extensions communicating to each other because you won't be on the same LAN, and this just adds new layers of difficulties and unnecessarily complicates things.

Axon keeps a record of all calls (including date, time, caller ID, etc.) in a file called Phone Log.csv (in Axon's Admin panel, go to logs, and it should be listed for download). You can open a CSV in various programs including wordpad/notepad if necessary.

That is up to you. An OGM in IVM can be easily programmed to automatically transfer after a period of time (e.g. 0 seconds), or to wait for input from the caller.

Correct. For telemarketing calls you could - Send out automated messages to various phone numbers Or - Have IVM dial numbers and greet the person with an OGM that automatically gets IVM to transfer the caller to someone who is available to answer in the call centre Please be aware and respect the laws of your area. In some places it may be illegal to make phone calls and deliver automated messages, or it may only be legal to do so if the person being called is already affiliated with you or is a consumer of your products for example.