1.3.2 to 2.0.3: Incoming DTMF (IPKall) not working

jandir

Joined
Aug 24, 2008
Messages
65
Likes
0
Points
0
#1
I upgraded my system from 1.3.2 to 2.0.3 and cut paste the same configuration for trunks, inbound routes, outbound routes, extensions, etc. However I had DISA setup with IPKall incoming trunks and now the DTMF tones are not recognized at all.

Not sure though if this is specific to IPKall. I don't use incoming DTMF for any other trunk or use.

The IPKall trunk configuration is (User details):
disallow=all
allow=ulaw,g729,gsm
dtmfmode=rfc2833

I have tried dtmfmode=info and inband with no effect.

Please help.

Thank you.
 

jandir

Joined
Aug 24, 2008
Messages
65
Likes
0
Points
0
#2
Re:1.4.2 to 2.0.3: Incoming DTMF (IPKall) not working

Fixed it. It was not a DTMF issue but a NAT issue and the call was not completing so no RTP was going through. I have not understood the reason completely, but the SIP ACK from IPKall was not coming back to elastix(?) and the change below fixed it. I had forgotten about all of the custom configuration that had to be done after installing a new system (should have documented it the first time!!). I am sure i am missing some more stuff like this.

Had to add the following to the configuration to get it to work. Earlier this used to be in the nat config file but with the new release the nat configuration goes into sip_general_custom.conf

[root@Elastix asterisk]# cat sip_general_custom.conf
bindport=5060
bindaddr=0.0.0.0
nat=yes
externhost=xxxxxx.homeip.net
localnet=192.168.1.40/255.255.255.0
externrefresh=10
allowguest=yes
context=from_internal
rtptimeout=60
rtpholdtimeout=120
useragent=Elastix
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,886
Members
17,563
Latest member
dineshr
Top