slantyyz

We have IVM working with Axon and a few SPA-3000 FXO adapters. The problem we've been having lately is related to an SPA-3000 issue. The SPA-3000 issue (which I didn't find out about until _after_ we bought IVM and the SPA hardware) is that they are prone to sending out random DTMF signals during calls. What happens with respect to IVM is that while a person is leaving a message, IVM detects that they're pressing "1" and then erases everything the person has said since they hit 1, unbeknownst to the caller. For me, short of replacing the entire phone system with something like Asterisk, my solutions are very limited. I can set the DTMF recognition to Inband on the SPA. Result: IVM doesn't recognize the DTMF sounds so that's an obvious no-go. Option 2 is to be able to disable extraneous DTMF signals or adjust sensitivity of the DTMF detection. Unfortunately, IVM doesn't really allow me to do either. These problems make our phone system seem like a Mickey Mouse organization to our clients, and I'm spending way more time than I should tweaking the phone system (makes us regret not buying a Nortel or Avaya solution that cost ten times as much as what we paid for the current setup). Does anyone know of any workarounds?

Has anyone experienced this: When an SPA3000 registers during an active call, Axon creates a 3-way call to the voicemail (we use IVM). All parties can hear the default greeting. Because the Line 1 and PSTN register one after another (1 second difference), it's hard to identify the true culprit, though I suspect it is the PSTN registration. Example: My Sipura shows registrations for Line 1 @ 12:28:16, PSTN @ 12:28:17, and IVM picks up the line at 12:28:30. The Axon log shows the external number calling the voicemail, ie: 12:28:30 Call sip:######### -> 199 (199 is the default extension for our IVM) -- Since registration occurs at preset intervals, I can predict when this problem will occur, but I'd rather not work around the interval and eliminate the issue altogether. Any feedback is appreciated. s

Check that the software latched onto the correct network adapter. The little log screen under the phone panel will show you what adapter it connected to. If you have more than one adapter (or virtual adapter, because of vmware, et al) then it usually latches on to the wrong one. The only thing you can do is disable all the other network adapaters in windows to get it to work. Not an optimal fix.

I spent hours trying to figure this out, and I have to agree. I'd rather that Expresstalk (as well as Axon and Uplink) figure out what your network addresses are and then just let you pick them from a list. When using these products with more than one NIC (physical or virtual), the apps are wrong 90% of the time.