Jump to content

2.1.5.2357 (win) had to revert..


andrewgroup
 Share

Recommended Posts

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)

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

  • 3 weeks later...

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

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 12 times

[9] 20080204154857: Resolve 9916814: udp 10.15.236.162 16626

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 9 times

[9] 20080204154857: Resolve 9916815: udp 15.10.174.19 5060

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 42 times

[9] 20080204154857: Resolve 9916816: udp 15.10.174.19 5060

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 17 times

[9] 20080204154857: Resolve 9916817: udp 10.15.237.138 10229

[9] 20080204154857: Resolve 9916818: udp 10.15.237.138 10244

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 6 times

[9] 20080204154857: Resolve 9916819: udp 15.10.174.19 5060

[8] 20080204154857: No codec available for sending

[8] 20080204154857: Last message repeated 21 times

[9] 20080204154857: Resolve 9916820: udp 10.15.237.138 10238

[8] 20080204154857: No codec available for sending

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...