[cisco-voip] DTMF issues with VG224 but not other phones (UPDATE)

Nick Matthews matthnick at gmail.com
Wed Apr 7 22:46:48 EDT 2010


A few notes:

Yes, the 'affected versions' field is normally not very accurate. It
will sometimes give you a better idea, but I would not rely on it.
Quite often the actual IOS release a bug started is never determined
for a number of reasons.

The SG3 feature is *software* based and not hardware, from what I
heard and read.  I didn't find a doc, but it is 15.1(1)T which just
released, and it supports PVDM2.

I would personally be much more worried about DSP crashes in a VG224
than someone internally sending specially crafted SCCP packets to it.

-nick

On Wed, Apr 7, 2010 at 8:53 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz49741
>
> says it's fixed in 12.4(15)T10
>
> wouldn't T11 have the same fixes as T10?
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
>                               - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Jason Aarons (US)" <jason.aarons at us.didata.com>
> To: "Nick Matthews" <matthnick at gmail.com>, "Nate VanMaren"
> <VanMarenNP at ldschurch.org>
> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
> Sent: Wednesday, April 7, 2010 8:44:39 PM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
> (UPDATE)
>
> 12.4.15T11 has the malformed SCCP vulnerability
> http://tools.cisco.com/security/center/viewAlert.x?alertId=20070 right?
>
> What issues around 12.5.15T12 are you seeing?
>
>
> -----Original Message-----
> From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick Matthews
> Sent: Wednesday, April 07, 2010 7:49 PM
> To: Nate VanMaren
> Cc: Peter Slow; Jason Aarons (US); cisco-voip voyp list
> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
> (UPDATE)
>
> As the person who primarily worked on CSCso87127, I can tell you with
> high confidence that is your issue.  upgrade to 12.4(15)T11 and you
> will be alright.  There are crashes in (15)T12, so I would avoid on
> gateways.  The 224 always has 5510 DSPs.
>
> -nick
>
> On Wed, Apr 7, 2010 at 6:29 PM, Nate VanMaren <VanMarenNP at ldschurch.org>
> wrote:
>> That ruins my year.
>>
>> -----Original Message-----
>> From: Peter Slow [mailto:peter.slow at gmail.com]
>> Sent: Wednesday, April 07, 2010 3:04 PM
>> To: Jason Aarons (US)
>> Cc: Nate VanMaren; Lelio Fulgenzi; Justin Steinberg; cisco-voip voyp list
>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>> (UPDATE)
>>
>> its the PVDM3
>>
>> On Wed, Apr 7, 2010 at 2:33 PM, Jason Aarons (US)
>> <jason.aarons at us.didata.com> wrote:
>>> Is it 15T or the hardware that comes with  x9xx (PVDM3)  that allows up
>>> to
>>> G3/33.3?  I didn't think 15T and VG224/SCCP would speed anything up.
>>>
>>>
>>>
>>> From: cisco-voip-bounces at puck.nether.net
>>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
>>> Sent: Wednesday, April 07, 2010 1:45 PM
>>> To: Lelio Fulgenzi; Justin Steinberg
>>> Cc: cisco-voip voyp list
>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>> (UPDATE)
>>>
>>>
>>>
>>> Nah, go to 15T so you can do faster faxes J
>>>
>>>
>>>
>>> From: cisco-voip-bounces at puck.nether.net
>>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
>>> Sent: Wednesday, April 07, 2010 11:43 AM
>>> To: Justin Steinberg
>>> Cc: cisco-voip voyp list
>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>> (UPDATE)
>>>
>>>
>>>
>>> 12.4(22)T is affected
>>>
>>>
>>> http://tools.cisco.com/Support/BugToolKit/search/knownAffectedVersions.do?method=fetchKnownAffectedVersions&bugId=CSCso87127
>>>
>>> I think I'm going to take baby steps here and upgrade to 12.4(15)T8 as
>>> suggested in the notes.
>>>
>>> ---
>>> Lelio Fulgenzi, B.A.
>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> Cooking with unix is easy. You just sed it and forget it.
>>>                               - LFJ (with apologies to Mr. Popeil)
>>>
>>>
>>> ----- Original Message -----
>>> From: "Justin Steinberg" <jsteinberg at gmail.com>
>>> To: "Peter Slow" <peter.slow at gmail.com>
>>> Cc: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "cisco-voip voyp list"
>>> <cisco-voip at puck.nether.net>
>>> Sent: Wednesday, April 7, 2010 1:31:15 PM GMT -05:00 US/Canada Eastern
>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>> (UPDATE)
>>>
>>> I think you are most definitely experiencing that bug.  upgrade your IOS
>>> to
>>> a fixed version, 12.4(22)T has some nice SCCP features.
>>>
>>> On Wed, Apr 7, 2010 at 1:09 PM, Peter Slow <peter.slow at gmail.com> wrote:
>>>
>>> honestly, if you listen closely, you might be able to hear it with a
>>> human ear. try a testcall to your cellphone from the ip phone, press a
>>> button, try again from the vg224 phone, press a button. I think it
>>> sounds like a continuous tone with a "blip" in the middle. it may just
>>> be clearly audible as two separate tones.
>>>
>>> actually, your working/non working scenarios make sense with that bug,
>>> since in the working scenario from an IP phone, there are never any
>>> DTMF digits in the RTP stream in the first place. (so its impossible
>>> to hit the bug.)
>>>
>>> I would do that test and then upgrade the 224 to 12.4(15)T8.
>>>
>>> On Wed, Apr 7, 2010 at 12:56 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
>>> wrote:
>>>> i knew it. i'll have to get my digital structures book out and build a
>>>> flip/flop switch to take care of that.
>>>>
>>>> call flow. yes. here it is. get ready. don't blink.
>>>>
>>>> farmer's fingers -> analog set -> VG224 (SCCP) port -> campus cloud ->
>>>> 3945
>>>> PRI (MGCP) -> PSTN -> Bank's IVR
>>>>
>>>> interesting part about the IVR reading back the numbers. i'll have to
>>>> check
>>>> that out.
>>>>
>>>>
>>>> ---
>>>> Lelio Fulgenzi, B.A.
>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> Cooking with unix is easy. You just sed it and forget it.
>>>>                               - LFJ (with apologies to Mr. Popeil)
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Peter Slow" <peter.slow at gmail.com>
>>>> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>>>> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
>>>> Sent: Wednesday, April 7, 2010 12:49:34 PM GMT -05:00 US/Canada Eastern
>>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>>> (UPDATE)
>>>>
>>>> obviously the F's are a problem. we can set them all to zeros with a
>>>> 9-volt battery and some copper wire. pop the cover off that bad boy
>>>> and we'll get started.
>>>>
>>>> Are you going to tell us about the call flow? =) how does the call
>>>> egress your network to get to the IVR?
>>>>
>>>> -Peter
>>>>
>>>> On Wed, Apr 7, 2010 at 12:44 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
>>>> wrote:
>>>>> pretty show diag output follows. i wonder if it's all those F's in
>>>>> there
>>>>> that are causing the problem. looks like way too many for me.
>>>>>
>>>>> ________________________________
>>>>> kc_vg224_no1>show diag
>>>>> VG224 Backplane EEPROM:
>>>>>         PCB Serial Number        : FOC1115449X
>>>>>         Processor type           : 7B
>>>>>         Top Assy. Part Number    : 800-24228-05
>>>>>         Board Revision           : B0
>>>>>         Fab Part Number          : 28-5952-03
>>>>>         Deviation Number         : 8-2097
>>>>>         Manufacturing Test Data  : FF FF FF FF FF FF FF FF
>>>>>         RMA Number               : 255-255-255-255
>>>>>         RMA Test History         : FF
>>>>>         RMA History              : FF
>>>>>         Chassis Serial Number    : FHK1118F0Z8
>>>>>         Chassis MAC Address      : 001a.e221.be33
>>>>>         MAC Address block size   : 5
>>>>>         Field Diagnostics Data   : FF FF FF FF FF FF FF FF
>>>>>         Hardware Revision        : 4.1
>>>>>         Number of Slots          : 1
>>>>>         Product (FRU) Number     : VG224
>>>>>         Version Identifier       : V02
>>>>>         EEPROM format version 4
>>>>>         EEPROM contents (hex):
>>>>>           0x00: 04 FF C1 8B 46 4F 43 31 31 31 35 34 34 39 58 09
>>>>>           0x10: 7B 40 04 5B C0 46 03 20 00 5E A4 05 42 42 30 85
>>>>>           0x20: 1C 17 40 03 80 00 08 08 31 C4 08 FF FF FF FF FF
>>>>>           0x30: FF FF FF 81 FF FF FF FF 03 FF 04 FF C2 8B 46 48
>>>>>           0x40: 4B 31 31 31 38 46 30 5A 38 C3 06 00 1A E2 21 BE
>>>>>           0x50: 33 43 00 05 C5 08 FF FF FF FF FF FF FF FF 41 04
>>>>>           0x60: 01 01 01 CB 85 56 47 32 32 34 89 56 30 32 00 FF
>>>>>           0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>>>>> Slot 0:
>>>>>         VG224 Motherboard 24FXS-2FE (3 onboard DSPs) Port adapter, 26
>>>>> ports
>>>>>         Port adapter is analyzed
>>>>>         Port adapter insertion time unknown
>>>>>         EEPROM contents at hardware discovery:
>>>>>         PCB Serial Number        : FOC1115449X
>>>>>         Processor type           : 7B
>>>>>         Top Assy. Part Number    : 800-24228-05
>>>>>         Board Revision           : B0
>>>>>         Fab Part Number          : 28-5952-03
>>>>>         Deviation Number         : 8-2097
>>>>>         Manufacturing Test Data  : FF FF FF FF FF FF FF FF
>>>>>         RMA Number               : 255-255-255-255
>>>>>         RMA Test History         : FF
>>>>>         RMA History              : FF
>>>>>         Chassis Serial Number    : FHK1118F0Z8
>>>>>         Chassis MAC Address      : 001a.e221.be33
>>>>>         MAC Address block size   : 5
>>>>>         Field Diagnostics Data   : FF FF FF FF FF FF FF FF
>>>>>         Hardware Revision        : 4.1
>>>>>         Number of Slots          : 1
>>>>>         Product (FRU) Number     : VG224
>>>>>         Version Identifier       : V02
>>>>>         EEPROM format version 4
>>>>>         EEPROM contents (hex):
>>>>>           0x00: 04 FF C1 8B 46 4F 43 31 31 31 35 34 34 39 58 09
>>>>>           0x10: 7B 40 04 5B C0 46 03 20 00 5E A4 05 42 42 30 85
>>>>>           0x20: 1C 17 40 03 80 00 08 08 31 C4 08 FF FF FF FF FF
>>>>>           0x30: FF FF FF 81 FF FF FF FF 03 FF 04 FF C2 8B 46 48
>>>>>           0x40: 4B 31 31 31 38 46 30 5A 38 C3 06 00 1A E2 21 BE
>>>>>           0x50: 33 43 00 05 C5 08 FF FF FF FF FF FF FF FF 41 04
>>>>>           0x60: 01 01 01 CB 85 56 47 32 32 34 89 56 30 32 00 FF
>>>>>           0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>>>>> ________________________________
>>>>> ---
>>>>> Lelio Fulgenzi, B.A.
>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>> Cooking with unix is easy. You just sed it and forget it.
>>>>>                               - LFJ (with apologies to Mr. Popeil)
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Peter Slow" <peter.slow at gmail.com>
>>>>> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>>>>> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
>>>>> Sent: Wednesday, April 7, 2010 12:38:44 PM GMT -05:00 US/Canada Eastern
>>>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>>>> (UPDATE)
>>>>>
>>>>> no you did not, i am clearly wrong about the DSPs in use in the VG224.
>>>>> could i see a show diag real quick, just for my own knowledge?
>>>>> if the symptoms described earlier match the ones you're seeing, your
>>>>> version is certainly susceptible to that bug.
>>>>>
>>>>> a quick way to tell if thats you issue, at least at that gateway, is
>>>>> to grab a packet capture of a g.711 testcall and rebuild it using
>>>>> wireshark. if you hear any dtmf tones in the RTP stream, you're
>>>>> hitting that bug.
>>>>>
>>>>> -Peter
>>>>>
>>>>> On Wed, Apr 7, 2010 at 12:28 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
>>>>> wrote:
>>>>>> Thanks Peter, here's what I get from one of my VG224s. Did I
>>>>>> incorrectly
>>>>>> assume I'm using C5510s because they're listed here? The chip type and
>>>>>> DSP
>>>>>> version match.
>>>>>>
>>>>>> ________________________________
>>>>>> kc_vg224_no1#show voice dsp voice
>>>>>>
>>>>>>
>>>>>> ----------------------------FLEX VOICE CARD 0
>>>>>> ------------------------------
>>>>>>                            *DSP VOICE CHANNELS*
>>>>>>
>>>>>> CURR STATE : (busy)inuse (b-out)busy out (bpend)busyout pending
>>>>>> LEGEND     : (bad)bad    (shut)shutdown  (dpend)download pending
>>>>>>
>>>>>> DSP   DSP              DSPWARE CURR  BOOT                         PAK
>>>>>> TX/RX
>>>>>> TYPE  NUM CH CODEC     VERSION STATE STATE   RST AI VOICEPORT TS ABRT
>>>>>> PACK
>>>>>> COUNT
>>>>>> ===== === == ========= ======= ===== ======= === == ========= == ====
>>>>>> ============
>>>>>> C5510 001 01 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 02 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 03 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 04 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 05 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 06 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 07 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 08 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 09 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 10 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 11 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 12 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 13 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 14 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 15 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 001 16 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 01 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 02 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 03 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 04 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 05 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 06 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 07 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 08 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 09 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 10 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 11 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 12 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 13 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 14 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 15 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 002 16 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 01 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 02 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 03 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 04 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 05 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 06 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 07 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 08 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 09 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 10 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 11 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 12 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 13 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 14 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 15 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>> C5510 003 16 None           9.4.5 idle  idle      0  0
>>>>>> 0          0/0
>>>>>>
>>>>>> ________________________________
>>>>>> ---
>>>>>> Lelio Fulgenzi, B.A.
>>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>> Cooking with unix is easy. You just sed it and forget it.
>>>>>>                               - LFJ (with apologies to Mr. Popeil)
>>>>>>
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Peter Slow" <peter.slow at gmail.com>
>>>>>> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>>>>>> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
>>>>>> Sent: Wednesday, April 7, 2010 12:22:08 PM GMT -05:00 US/Canada
>>>>>> Eastern
>>>>>> Subject: Re: [cisco-voip] DTMF issues with VG224 but not other phones
>>>>>> (UPDATE)
>>>>>>
>>>>>> Lelio,
>>>>>>    that bug is specific to the 5510 DSPs according to the information
>>>>>> in it, your VG224 is equipped with the original PVDMs, which are
>>>>>> c549s, unless there's an HDV2 in it, which im not sure is possible. a
>>>>>> show diag will tell you. Also, theres a very specific symptom with
>>>>>> that bug; at the far end the digits are detected twice. if you are
>>>>>> entering your account number, and press 123, the IVR will tell you it
>>>>>> detected 112233. Is that symptom or somethign similar being reported??
>>>>>>    Is there any sip involved in your environment? tell us more about
>>>>>> the call flow and what devices that call is traversing. from what
>>>>>> you've said, it sounds liek the end users are plugged into the 224.
>>>>>> I'd like to understand how the call is leaving your voice network.
>>>>>> (SIP Trunk, MGCP gateway, etc)
>>>>>>
>>>>>> -Peter
>>>>>>
>>>>>>
>>>>>> On Tue, Apr 6, 2010 at 7:33 PM, Lelio Fulgenzi <lelio at uoguelph.ca>
>>>>>> wrote:
>>>>>>> looks like i might be running into this bug?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCso87127
>>>>>>>
>>>>>>> ---
>>>>>>> Lelio Fulgenzi, B.A.
>>>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>>>>>>
>>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>> Cooking with unix is easy. You just sed it and forget it.
>>>>>>>                               - LFJ (with apologies to Mr. Popeil)
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>>>>>>> To: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
>>>>>>> Sent: Tuesday, April 6, 2010 4:47:53 PM GMT -05:00 US/Canada Eastern
>>>>>>> Subject: DTMF issues with VG224 but not other phones (UPDATE)
>>>>>>>
>>>>>>> UPDATE: I've included the version and config of the vg224.
>>>>>>>
>>>>>>> We have a user who is having problems using a calling card. They are
>>>>>>> able
>>>>>>> to
>>>>>>> traverse the tree successfully up until a point, so they enter 1 for
>>>>>>> English, etc. but they have an issue where they enter their calling
>>>>>>> card
>>>>>>> number.
>>>>>>>
>>>>>>> The problem is reproducible (as far as I know) across multiple VG224
>>>>>>> ports
>>>>>>> and multiple VG224s. The problem is eliminated when using an IP
>>>>>>> phone.
>>>>>>>
>>>>>>> I gather that it does not have anything to do with the PSTN gateways
>>>>>>> per
>>>>>>> se
>>>>>>> (since it works with IP phones) but more an issue with VG224 config.
>>>>>>>
>>>>>>> I'm getting more information from the client, but just wondering if
>>>>>>> anyone
>>>>>>> has any suggestions.
>>>>>>>
>>>>>>> I've done some searching on netpro forums and found the following
>>>>>>> debug
>>>>>>> statements to be useful:
>>>>>>>
>>>>>>> debug vpm signal (very simple output)
>>>>>>> debug voip vtsp dsp (a bit more detailed - provides the in/out)
>>>>>>> debug voip ccapi inout (even more detailed)
>>>>>>>
>>>>>>> Any suggestions would be great.
>>>>>>>
>>>>>>> Lelio
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---
>>>>>>> Lelio Fulgenzi, B.A.
>>>>>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>>>>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>>>>>>>
>>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>> Cooking with unix is easy. You just sed it and forget it.
>>>>>>>                               - LFJ (with apologies to Mr. Popeil)
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cisco-voip mailing list
>>>>>>> cisco-voip at puck.nether.net
>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>> NOTICE: This email message is for the sole use of the intended
>>> recipient(s)
>>> and may contain confidential and privileged information. Any unauthorized
>>> review, use, disclosure or distribution is prohibited. If you are not the
>>> intended recipient, please contact the sender by reply email and destroy
>>> all
>>> copies of the original message.
>>>
>>>
>>>
>>> ________________________________
>>>
>>> Disclaimer: This e-mail communication and any attachments may contain
>>> confidential and privileged information and is for use by the designated
>>> addressee(s) named above only. If you are not the intended addressee, you
>>> are hereby notified that you have received this communication in error
>>> and
>>> that any use or reproduction of this email or its contents is strictly
>>> prohibited and may be unlawful. If you have received this communication
>>> in
>>> error, please notify us immediately by replying to this message and
>>> deleting
>>> it from your computer. Thank you.
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>>
>>  NOTICE: This email message is for the sole use of the intended
>> recipient(s) and may contain confidential and privileged information. Any
>> unauthorized review, use, disclosure or distribution is prohibited. If you
>> are not the intended recipient, please contact the sender by reply email and
>> destroy all copies of the original message.
>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>



More information about the cisco-voip mailing list