ygeffens

Before I started using Axon PBX:

Call to a service number. They ask to press 1 for this, 2 for that...

No problem. These keys pressed are called DTMF-tones (here in Belgium), I don't know if that is a worldwide used name.

Now after installing Axon and registering the phones with Axon, these pressed keys are not understood by the other party. Axon uses the same SIP gateway as previously used with my ATA (Avm FritzBox WLAN).

The other party receives the tone, but in some compressed form, not "clear" enough to be decoded (to know the pressed key).

When routing that specific call over the fixed line, the problem is gone.

Having the AVM Fritzbox connecting directly (again) to my SIP gateway, also, the problem is gone.

First I was thinking it was caused because Axon registered with a different codec at my SIP gateway, but in the FAQ that it supports "all" codecs.

Any help is appreciated, because it's "anoying" having to route these specific numbers through my fixed line.

Even worse, callers to my shop have the possibility to choose: 1 for Shop, 2 for technical Deptartment. This is not functioning either. Just to say that it's also for people dialing in from a fixed phone.

Thanks !

Yves

I wish that NCH took the habit of placing all revision numbers and release dates on their website so that we can easily determine if a new release is out or not.  I dislike the fact that I must constantly download the files and install them to find out that they are still not updated.  Waste of my time and NCH's Bandwidth.

 

It is not hard to create a separate organized download page with all available downloads with their release dates and also keep 1-2 back revisions within the list incase the new release does not work for someone.

 

Can this be fixed soon?

<{POST_SNAPBACK}>

I totally agree. NCH, please ? :-)

Thanks !