Topic: Problems with IVR on a remote PBX

[soprom]

I have problems with IVR on a remote system. When the call (outgoing) is established and I need to dial a digit to answer the remote IVR, it does not get some of my entries (digit 1 for example is not understood, but 2 is).

I use a SIP extension on Aastra 480iCT on an IAX trunk to my provider.

Anyone experienced this kind of problem?
 

[SARK devs]

This can be caused by an incorrect DTMF setting, either in the phone or in sip.conf.  Check that the dtmf set in the phone matches dtmfmode= in sip.conf.  Also, make sure that you are not attempting to use in-band DTMF with a compressive CODEC such as G729 (won't work).

The only other possible cause is if you have any in-band feature enhancements to asterisk.  These appear in features.conf and cause Asterisk to listen for specific key presses during a call (hash transfer is an example of a feature).

Usually one of these two.

Best

S   

[soprom]

The Aastra 480iCT has these:
Force RFC2833 Out-of-Band DTMF : enabled
DTMF Method: rtp ("sip info" available)

sip.conf has no DTMF options

I'll test with "sip info".

Thanks for your hints!

[compsos]

Hi Sophie

Do you have "Call Recording System". We had that problem when it is active as it uses "1" to activate recording. Jeff suggested making it something else but if you use 2 numbers you will have to hit the keys quickly to register for recording.

[soprom]

Yes indeed! Call Recording System Default is set to OTR.

features.conf :

Code: [Select]

[general]
parkext=>*5
parkpos=>101-104
context=>parkedcalls
parkingtime=>180
transferdigittimeout=>3
courtesytone=beep
;adsipark=yes
pickupexten=*8
[featuremap]
blindxfer=>##
;disconnect=>*0
automon=>1
;atxfer=*2
language=fr
Could you tell me how to set this OTR to a different digit?

Thanks!

[SARK devs]

automon=

set it to whatever key sequence you want.  We tend to use *6 and program it into the record button on our Snoms, you can use whatever feature key you have spare or just tap it in manually.

If you are going to use more than one keypress then by default, Asterisk will only give you 500ms between keypresses.  If this is too aggressive you can set it to a longer value with

featuredigittimeout=n (miliseconds)

e.g. featuredigittimeout=1000  will give you up to 1 second between key presses.

 Best

S

[soprom]

Thanks for this info...

I understand that it must be changed directly through the "headers" menu and that this change will not survive updates.

[SARK devs]

currently features.conf may not survive a software update.  You will need to re-input the change if we make a change to features.  We don't do it very often but we do change it from time to time.