2.1.5.2357 (win) had to revert..

andrewgroup · January 11, 2008

We did an inplace upgrade on our internal system and after a day or so we discovered our Main AA wasn't recognizing inband DTMF signalling, thus the caller could not select a department. We were no aware of any changes other than the upgrade. Rolled back to previous all is good again.

Prior to rolling back, though we did some log troubleshooting and were not able to find a log setting that would indicate the DTMF tones were being detected. Does this exists, and I suppose if it did it would come from the same place that the PBX gets it and, thus DTMF either works or it doesn't.

Same config 2.03 works as expected and 2.1.5 worked (spotily)

Vodia PBX · January 11, 2008

Whow. Does the PSTN gateway negotiate out of band DTMF (should be visible in the initial INVITE coming to the PBX)?

andrewgroup · January 11, 2008

No Gateways, Pure SIP trunks to our Provider. We can easily perform this again in a controlled tested and perform any number of tests. We did change the DTMF in-out of band settings, and start/stop service to no avail. Any tips to perform in a controlled retest away from the panic of the unexpected discovery would be appreciated.

Vodia PBX · January 12, 2008

Yea I would recommend to do a test setup and get an Ethereal trace. There must be something wrong with the negotiation of out of band DTMF.

ap_6200 · January 18, 2008

Is there any update to this?

I recently discovered that 2.1.4 has inband DTMF issues - when calling certain 800 #'s - and using the Touch Tone Response systems - The system was not able to identify all of the digits.

We tested this same number from version 2.0.3.1715 FS, and from the test system 2.1.5.2357 and it worked fine.

Are there any outstanding issues with 2.1.5.2357 that i should be aware of?

hosted · January 19, 2008

I still cant get inband DTMF from CMDA cell phones on 2.1.5.2357. I dont see a CS410 version of 2.0.3 to roll back to test with. luckly for me the ITSP we sell to is upgrading to RFC2833 on the Jan25th. <phew>

ap_6200 · February 4, 2008

Duplicate Ticket - but I want to make sure my voice is heard.

Is there a known issue with this and is it being fixed?

The proof is in the pudding for me... same exact setup - using 2.0.3.1715 - it works.

Using 2.1.5.2357 - doesn't work.

[8] 20080204154855: No codec available for sending

[8] 20080204154855: Last message repeated 45 times

[9] 20080204154855: Resolve 9916807: udp 10.15.237.246 1240

[8] 20080204154855: No codec available for sending

[8] 20080204154855: Last message repeated 6 times

[9] 20080204154855: Resolve 9916808: udp 15.10.174.19 5060

[8] 20080204154855: No codec available for sending

[8] 20080204154855: Last message repeated 12 times

[9] 20080204154855: Resolve 9916809: udp 15.10.174.19 5060

[8] 20080204154855: No codec available for sending

[8] 20080204154856: Last message repeated 58 times

[9] 20080204154856: Resolve 9916810: udp 10.15.237.138 10283

[8] 20080204154856: No codec available for sending

[8] 20080204154856: Last message repeated 32 times

[9] 20080204154856: Resolve 9916811: udp 10.15.237.234 49161

[8] 20080204154856: No codec available for sending

[8] 20080204154856: Last message repeated 61 times

[8] 20080204154856: SNMP: Received unknown object identifier 06082b06010201010300

[8] 20080204154856: No codec available for sending

[8] 20080204154856: Last message repeated 14 times

[9] 20080204154856: Resolve 9916812: udp 10.15.236.70 4217

[8] 20080204154856: No codec available for sending

[8] 20080204154857: Last message repeated 49 times

[9] 20080204154857: Resolve 9916813: udp 15.10.174.19 5060