<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>It's at a remote site (read barn) so the amount of troubleshooting available is limited.<br><br>I'm thinking of just upgrading and going from there.<br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message -----<br>From: "Peter Slow" <peter.slow@gmail.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Wednesday, April 7, 2010 1:09:19 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones (UPDATE)<br><br>honestly, if you listen closely, you might be able to hear it with a<br>human ear. try a testcall to your cellphone from the ip phone, press a<br>button, try again from the vg224 phone, press a button. I think it<br>sounds like a continuous tone with a "blip" in the middle. it may just<br>be clearly audible as two separate tones.<br><br>actually, your working/non working scenarios make sense with that bug,<br>since in the working scenario from an IP phone, there are never any<br>DTMF digits in the RTP stream in the first place. (so its impossible<br>to hit the bug.)<br><br>I would do that test and then upgrade the 224 to 12.4(15)T8.<br><br>On Wed, Apr 7, 2010 at 12:56 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>> i knew it. i'll have to get my digital structures book out and build a<br>> flip/flop switch to take care of that.<br>><br>> call flow. yes. here it is. get ready. don't blink.<br>><br>> farmer's fingers -> analog set -> VG224 (SCCP) port -> campus cloud -> 3945<br>> PRI (MGCP) -> PSTN -> Bank's IVR<br>><br>> interesting part about the IVR reading back the numbers. i'll have to check<br>> that out.<br>><br>><br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> Cooking with unix is easy. You just sed it and forget it.<br>> - LFJ (with apologies to Mr. Popeil)<br>><br>><br>> ----- Original Message -----<br>> From: "Peter Slow" <peter.slow@gmail.com><br>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>> Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>> Sent: Wednesday, April 7, 2010 12:49:34 PM GMT -05:00 US/Canada Eastern<br>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones<br>> (UPDATE)<br>><br>> obviously the F's are a problem. we can set them all to zeros with a<br>> 9-volt battery and some copper wire. pop the cover off that bad boy<br>> and we'll get started.<br>><br>> Are you going to tell us about the call flow? =) how does the call<br>> egress your network to get to the IVR?<br>><br>> -Peter<br>><br>> On Wed, Apr 7, 2010 at 12:44 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>>> pretty show diag output follows. i wonder if it's all those F's in there<br>>> that are causing the problem. looks like way too many for me.<br>>><br>>> ________________________________<br>>> kc_vg224_no1>show diag<br>>> VG224 Backplane EEPROM:<br>>> PCB Serial Number : FOC1115449X<br>>> Processor type : 7B<br>>> Top Assy. Part Number : 800-24228-05<br>>> Board Revision : B0<br>>> Fab Part Number : 28-5952-03<br>>> Deviation Number : 8-2097<br>>> Manufacturing Test Data : FF FF FF FF FF FF FF FF<br>>> RMA Number : 255-255-255-255<br>>> RMA Test History : FF<br>>> RMA History : FF<br>>> Chassis Serial Number : FHK1118F0Z8<br>>> Chassis MAC Address : 001a.e221.be33<br>>> MAC Address block size : 5<br>>> Field Diagnostics Data : FF FF FF FF FF FF FF FF<br>>> Hardware Revision : 4.1<br>>> Number of Slots : 1<br>>> Product (FRU) Number : VG224<br>>> Version Identifier : V02<br>>> EEPROM format version 4<br>>> EEPROM contents (hex):<br>>> 0x00: 04 FF C1 8B 46 4F 43 31 31 31 35 34 34 39 58 09<br>>> 0x10: 7B 40 04 5B C0 46 03 20 00 5E A4 05 42 42 30 85<br>>> 0x20: 1C 17 40 03 80 00 08 08 31 C4 08 FF FF FF FF FF<br>>> 0x30: FF FF FF 81 FF FF FF FF 03 FF 04 FF C2 8B 46 48<br>>> 0x40: 4B 31 31 31 38 46 30 5A 38 C3 06 00 1A E2 21 BE<br>>> 0x50: 33 43 00 05 C5 08 FF FF FF FF FF FF FF FF 41 04<br>>> 0x60: 01 01 01 CB 85 56 47 32 32 34 89 56 30 32 00 FF<br>>> 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF<br>>> Slot 0:<br>>> VG224 Motherboard 24FXS-2FE (3 onboard DSPs) Port adapter, 26<br>>> ports<br>>> Port adapter is analyzed<br>>> Port adapter insertion time unknown<br>>> EEPROM contents at hardware discovery:<br>>> PCB Serial Number : FOC1115449X<br>>> Processor type : 7B<br>>> Top Assy. Part Number : 800-24228-05<br>>> Board Revision : B0<br>>> Fab Part Number : 28-5952-03<br>>> Deviation Number : 8-2097<br>>> Manufacturing Test Data : FF FF FF FF FF FF FF FF<br>>> RMA Number : 255-255-255-255<br>>> RMA Test History : FF<br>>> RMA History : FF<br>>> Chassis Serial Number : FHK1118F0Z8<br>>> Chassis MAC Address : 001a.e221.be33<br>>> MAC Address block size : 5<br>>> Field Diagnostics Data : FF FF FF FF FF FF FF FF<br>>> Hardware Revision : 4.1<br>>> Number of Slots : 1<br>>> Product (FRU) Number : VG224<br>>> Version Identifier : V02<br>>> EEPROM format version 4<br>>> EEPROM contents (hex):<br>>> 0x00: 04 FF C1 8B 46 4F 43 31 31 31 35 34 34 39 58 09<br>>> 0x10: 7B 40 04 5B C0 46 03 20 00 5E A4 05 42 42 30 85<br>>> 0x20: 1C 17 40 03 80 00 08 08 31 C4 08 FF FF FF FF FF<br>>> 0x30: FF FF FF 81 FF FF FF FF 03 FF 04 FF C2 8B 46 48<br>>> 0x40: 4B 31 31 31 38 46 30 5A 38 C3 06 00 1A E2 21 BE<br>>> 0x50: 33 43 00 05 C5 08 FF FF FF FF FF FF FF FF 41 04<br>>> 0x60: 01 01 01 CB 85 56 47 32 32 34 89 56 30 32 00 FF<br>>> 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF<br>>> ________________________________<br>>> ---<br>>> Lelio Fulgenzi, B.A.<br>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>>> Cooking with unix is easy. You just sed it and forget it.<br>>> - LFJ (with apologies to Mr. Popeil)<br>>><br>>><br>>> ----- Original Message -----<br>>> From: "Peter Slow" <peter.slow@gmail.com><br>>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>> Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>>> Sent: Wednesday, April 7, 2010 12:38:44 PM GMT -05:00 US/Canada Eastern<br>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones<br>>> (UPDATE)<br>>><br>>> no you did not, i am clearly wrong about the DSPs in use in the VG224.<br>>> could i see a show diag real quick, just for my own knowledge?<br>>> if the symptoms described earlier match the ones you're seeing, your<br>>> version is certainly susceptible to that bug.<br>>><br>>> a quick way to tell if thats you issue, at least at that gateway, is<br>>> to grab a packet capture of a g.711 testcall and rebuild it using<br>>> wireshark. if you hear any dtmf tones in the RTP stream, you're<br>>> hitting that bug.<br>>><br>>> -Peter<br>>><br>>> On Wed, Apr 7, 2010 at 12:28 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>>>> Thanks Peter, here's what I get from one of my VG224s. Did I incorrectly<br>>>> assume I'm using C5510s because they're listed here? The chip type and<br>>>> DSP<br>>>> version match.<br>>>><br>>>> ________________________________<br>>>> kc_vg224_no1#show voice dsp voice<br>>>><br>>>><br>>>> ----------------------------FLEX VOICE CARD 0<br>>>> ------------------------------<br>>>> *DSP VOICE CHANNELS*<br>>>><br>>>> CURR STATE : (busy)inuse (b-out)busy out (bpend)busyout pending<br>>>> LEGEND : (bad)bad (shut)shutdown (dpend)download pending<br>>>><br>>>> DSP DSP DSPWARE CURR BOOT PAK<br>>>> TX/RX<br>>>> TYPE NUM CH CODEC VERSION STATE STATE RST AI VOICEPORT TS ABRT<br>>>> PACK<br>>>> COUNT<br>>>> ===== === == ========= ======= ===== ======= === == ========= == ====<br>>>> ============<br>>>> C5510 001 01 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 02 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 03 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 04 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 05 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 06 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 07 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 08 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 09 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 10 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 11 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 12 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 13 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 14 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 15 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 001 16 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 01 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 02 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 03 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 04 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 05 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 06 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 07 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 08 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 09 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 10 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 11 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 12 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 13 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 14 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 15 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 002 16 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 01 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 02 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 03 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 04 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 05 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 06 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 07 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 08 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 09 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 10 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 11 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 12 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 13 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 14 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 15 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>> C5510 003 16 None 9.4.5 idle idle 0 0<br>>>> 0 0/0<br>>>><br>>>> ________________________________<br>>>> ---<br>>>> Lelio Fulgenzi, B.A.<br>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>>>> Cooking with unix is easy. You just sed it and forget it.<br>>>> - LFJ (with apologies to Mr. Popeil)<br>>>><br>>>><br>>>> ----- Original Message -----<br>>>> From: "Peter Slow" <peter.slow@gmail.com><br>>>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>>> Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>>>> Sent: Wednesday, April 7, 2010 12:22:08 PM GMT -05:00 US/Canada Eastern<br>>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones<br>>>> (UPDATE)<br>>>><br>>>> Lelio,<br>>>> that bug is specific to the 5510 DSPs according to the information<br>>>> in it, your VG224 is equipped with the original PVDMs, which are<br>>>> c549s, unless there's an HDV2 in it, which im not sure is possible. a<br>>>> show diag will tell you. Also, theres a very specific symptom with<br>>>> that bug; at the far end the digits are detected twice. if you are<br>>>> entering your account number, and press 123, the IVR will tell you it<br>>>> detected 112233. Is that symptom or somethign similar being reported??<br>>>> Is there any sip involved in your environment? tell us more about<br>>>> the call flow and what devices that call is traversing. from what<br>>>> you've said, it sounds liek the end users are plugged into the 224.<br>>>> I'd like to understand how the call is leaving your voice network.<br>>>> (SIP Trunk, MGCP gateway, etc)<br>>>><br>>>> -Peter<br>>>><br>>>><br>>>> On Tue, Apr 6, 2010 at 7:33 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>>>>> looks like i might be running into this bug?<br>>>>><br>>>>><br>>>>><br>>>>><br>>>>> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCso87127<br>>>>><br>>>>> ---<br>>>>> Lelio Fulgenzi, B.A.<br>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>>>>> Cooking with unix is easy. You just sed it and forget it.<br>>>>> - LFJ (with apologies to Mr. Popeil)<br>>>>><br>>>>><br>>>>> ----- Original Message -----<br>>>>> From: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>>>> To: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>>>>> Sent: Tuesday, April 6, 2010 4:47:53 PM GMT -05:00 US/Canada Eastern<br>>>>> Subject: DTMF issues with VG224 but not other phones (UPDATE)<br>>>>><br>>>>> UPDATE: I've included the version and config of the vg224.<br>>>>><br>>>>> We have a user who is having problems using a calling card. They are<br>>>>> able<br>>>>> to<br>>>>> traverse the tree successfully up until a point, so they enter 1 for<br>>>>> English, etc. but they have an issue where they enter their calling card<br>>>>> number.<br>>>>><br>>>>> The problem is reproducible (as far as I know) across multiple VG224<br>>>>> ports<br>>>>> and multiple VG224s. The problem is eliminated when using an IP phone.<br>>>>><br>>>>> I gather that it does not have anything to do with the PSTN gateways per<br>>>>> se<br>>>>> (since it works with IP phones) but more an issue with VG224 config.<br>>>>><br>>>>> I'm getting more information from the client, but just wondering if<br>>>>> anyone<br>>>>> has any suggestions.<br>>>>><br>>>>> I've done some searching on netpro forums and found the following debug<br>>>>> statements to be useful:<br>>>>><br>>>>> debug vpm signal (very simple output)<br>>>>> debug voip vtsp dsp (a bit more detailed - provides the in/out)<br>>>>> debug voip ccapi inout (even more detailed)<br>>>>><br>>>>> Any suggestions would be great.<br>>>>><br>>>>> Lelio<br>>>>><br>>>>><br>>>>><br>>>>> ---<br>>>>> Lelio Fulgenzi, B.A.<br>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>>>>> Cooking with unix is easy. You just sed it and forget it.<br>>>>> - LFJ (with apologies to Mr. Popeil)<br>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> cisco-voip mailing list<br>>>>> cisco-voip@puck.nether.net<br>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>>>><br>>>>><br>>>><br>>><br>><br></div></body></html>