[cisco-voip] DTMF Method 0

[Anthony Holloway]

Ryan,

I see what you are saying, however, the call is setup (SIP) with media
exchanged and a media resource is inserted to help the call along.

I'll dig in more and let you know what comes of this.  Thanks for the input.


On Thu, May 23, 2013 at 9:53 AM, Ryan Ratliff <rratliff at cisco.com> wrote:

> Bugs aside, from what I can tell if you wee this then we haven't settled
> on a DTMF capability yet.  That would also explain why you miss the first
> digit, if something is getting delayed.
>
> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
> Outbound DTMF method not supported
>
>
>
> -Ryan
>
> On May 23, 2013, at 9:58 AM, Chris Ward (chrward) <chrward at cisco.com>
> wrote:
>
> Should have noted, the defect has to do with negotiating OOB and 2833 in
> the same call with a SIP trunk that has “no preference” selected as its
> DTMF method. You could try and select a preference and see if it resolved
> it. But again, we need your version to confirm.****
>
> +Chris****
> Unity Connection TME****
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Chris Ward (chrward)
> *Sent:* Thursday, May 23, 2013 9:50 AM
> *To:* Anthony Holloway; Cisco VoIP Group
> *Subject:* Re: [cisco-voip] DTMF Method 0****
> ** **
> Anthony,****
>
> For issues like these, the call flow and devices involved in the call flow
> are crucial. On a quick internal search, I found CSCuc80321 with the same
> error/warning. We would need your version too.****
>
> +Chris****
> Unity Connection TME****
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>
> ] *On Behalf Of *Anthony Holloway
> *Sent:* Thursday, May 23, 2013 12:26 AM
> *To:* Cisco VoIP Group
> *Subject:* [cisco-voip] DTMF Method 0****
> ** **
>
> All,****
> *The smaller picture*****
>
>
> I have the following two lines from a CCM trace I pulled:****
> 00:06:11.643
> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
> Outbound DTMF method selected is 0. Digit=1 and
> isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107
> 00:06:11.643
> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
> Outbound DTMF method not supported
> (0)|5,200,21,1.12763334^[REDACTED]^RCP5143F0107****
> ** **
> The log states that this method is not supported, but what is the method
> exactly?****
> ** **
> *The bigger picture*****
> ** **
>
> My Mobile Agent Connect Tone feature is half working, and I can see DTMF
> digits 1 and 2 being sent in the Agent's direction, however, the Agent is
> only hearing the second tone.  I have confirmed this with the above trace
> lines showing that the first tone fails due to unsupported reasons, also
> the below additional trace lines showing the second tone being sent via a
> different method and succeeding, and finally, a wireshark capture which
> only shows the digit 2 hitting the wire as RTP-NTE (not shared).****
> 00:06:11.905
> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/star_CcUserInfoReq:
> Outbound DTMF method selected is 2. Digit=2 and
> isMTPPassingThru2833=0|5,200,21,1.12763334^[REDACTED]^RCP5143F0107
> 00:06:11.905
> |//SIP/SIPCdpc(8,74,1872820)/ci=146637572/ccbId=85511580/scbId=0/sendDtmfVia2833:
> sending sipOutgoingDTMFTone Tone 2 for digit
> 2.|5,200,21,1.12763334^[REDACTED]^RCP5143F0107****
> ** **
> If I could figure out the method number to name mapping, that would help
> me understand why method 0 is not supported while method 2 is.
>
> Thanks for your help.****
> ** **
> Anthony Holloway****
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/443bda7d/attachment.html>