Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. telepresence (Erick Wellnitz)
2. Re: DTMF Method 0 (Anthony Holloway)
3. Re: DTMF Method 0 (Anthony Holloway)
4. Re: DTMF Method 0 (Anthony Holloway)
5. Re: DTMF Method 0 (Nick Matthews)
6. Connecting Cisco 2911 Voice Gateway to Amplified sound system
([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 23 May 2013 11:33:42 -0500
From: Erick Wellnitz <[email protected]>
To: cisco-voip <[email protected]>
Subject: [cisco-voip] telepresence
Message-ID:
<cak0wosamnevwqai2q2etdjyk33ffpot-el6881-gu_8jo6u...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
A little off topic but very closely related.
Does anyone have some good sources for reading and learning the details of
the telepresence offerings?
Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/eec6ea51/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 23 May 2013 22:54:45 -0500
From: Anthony Holloway <[email protected]>
To: Nick Matthews <[email protected]>
Cc: Cisco VoIP Group <[email protected]>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
<CACRCJOju_DQ-Vs_k2+6L51q6=64+ou9wiqtinxhnr2ohfqu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Just to clarify, what if it were a transcoder and not an MTP? See, the PG
is set to g729 (mistake) and the ACME SBC is set to g711 only (call
recording), therefore a transcoder is what gets used.
On Thu, May 23, 2013 at 10:41 PM, Nick Matthews <[email protected]> wrote:
> Having some experience troubleshooting Mobile Agent issues I know at least
> in 8.0 MTP is required for the official UCCE Mobile Agent feature. A lack
> of MTP for this type of call flow could cause DTMF problems.
>
> -nick
>
>
> On Thu, May 23, 2013 at 11:11 AM, Chris Ward (chrward)
> <[email protected]>wrote:
>
>> According to the bug that is the defect, that DTMF input is trying to
>> be processed while the method is still undecided? The defect does have some
>> conditions that are different than what is presented here but it is still
>> pretty close.****
>>
>> ** **
>>
>> Having the DTMF preference selected as RFC2833 is supposed to be a
>> workaround but it either was applied without rebooting the trunk, there is
>> another caveat, or this is not the bug.****
>>
>> ** **
>>
>> The other thing you could try, IF this is the defect it should only occur
>> if Early Offer is enabled. Disabling Early Offer should work around it.**
>> **
>>
>> ** **
>>
>> This defect, as it stands now, is only going to be fixed in 9.1(2) and
>> 10.0(1) so if you wanted it in an 8.6(2) ES you would need to open a TAC
>> case and request the fix be ported to the ES.****
>>
>> ** **
>>
>> +Chris****
>>
>> Unity Connection TME****
>>
>> ** **
>>
>> *From:* Ryan Ratliff (rratliff)
>> *Sent:* Thursday, May 23, 2013 10:53 AM
>> *To:* Anthony Holloway
>> *Cc:* Cisco VoIP Group; Chris Ward (chrward)
>>
>> *Subject:* Re: [cisco-voip] DTMF Method 0****
>>
>> ** **
>>
>> 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) <[email protected]>
>> 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:[email protected]] *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:[email protected]<[email protected]>
>> ] *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
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/cisco-voip****
>>
>> ** **
>>
>> _______________________________________________
>> cisco-voip mailing list
>> [email protected]
>> 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/7be07248/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 23 May 2013 22:55:31 -0500
From: Anthony Holloway <[email protected]>
To: "Chris Ward (chrward)" <[email protected]>
Cc: Cisco VoIP Group <[email protected]>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
<cacrcjojmfx+v8d+usdu57hwod9q-ktjkpxaie7cndrry9tx...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks Chris, this is really good information. I will take the suggestions
and look at what my options are. I'll let you know.
On Thu, May 23, 2013 at 10:11 AM, Chris Ward (chrward) <[email protected]>wrote:
> According to the bug that is the defect, that DTMF input is trying to be
> processed while the method is still undecided? The defect does have some
> conditions that are different than what is presented here but it is still
> pretty close.****
>
> ** **
>
> Having the DTMF preference selected as RFC2833 is supposed to be a
> workaround but it either was applied without rebooting the trunk, there is
> another caveat, or this is not the bug.****
>
> ** **
>
> The other thing you could try, IF this is the defect it should only occur
> if Early Offer is enabled. Disabling Early Offer should work around it.***
> *
>
> ** **
>
> This defect, as it stands now, is only going to be fixed in 9.1(2) and
> 10.0(1) so if you wanted it in an 8.6(2) ES you would need to open a TAC
> case and request the fix be ported to the ES.****
>
> ** **
>
> +Chris****
>
> Unity Connection TME****
>
> ** **
>
> *From:* Ryan Ratliff (rratliff)
> *Sent:* Thursday, May 23, 2013 10:53 AM
> *To:* Anthony Holloway
> *Cc:* Cisco VoIP Group; Chris Ward (chrward)
>
> *Subject:* Re: [cisco-voip] DTMF Method 0****
>
> ** **
>
> 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) <[email protected]>
> 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:[email protected]] *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:[email protected]<[email protected]>
> ] *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
> [email protected]
> 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/f934b70f/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 23 May 2013 22:56:44 -0500
From: Anthony Holloway <[email protected]>
To: Ryan Ratliff <[email protected]>
Cc: Cisco VoIP Group <[email protected]>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
<cacrcjoj92zf4hqx_au9er+pci0l_qbmjon+_ckatmyx36ys...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 <[email protected]> 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) <[email protected]>
> 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:[email protected]] *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:[email protected]<[email protected]>
> ] *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
> [email protected]
> 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-0001.html>
------------------------------
Message: 5
Date: Thu, 23 May 2013 23:41:32 -0400
From: Nick Matthews <[email protected]>
To: "Chris Ward (chrward)" <[email protected]>
Cc: Cisco VoIP Group <[email protected]>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
<CAM-K-Nq=oyfa6g_yop9n6vyrndzgsgucblprize2eamn7gs...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Having some experience troubleshooting Mobile Agent issues I know at least
in 8.0 MTP is required for the official UCCE Mobile Agent feature. A lack
of MTP for this type of call flow could cause DTMF problems.
-nick
On Thu, May 23, 2013 at 11:11 AM, Chris Ward (chrward) <[email protected]>wrote:
> According to the bug that is the defect, that DTMF input is trying to be
> processed while the method is still undecided? The defect does have some
> conditions that are different than what is presented here but it is still
> pretty close.****
>
> ** **
>
> Having the DTMF preference selected as RFC2833 is supposed to be a
> workaround but it either was applied without rebooting the trunk, there is
> another caveat, or this is not the bug.****
>
> ** **
>
> The other thing you could try, IF this is the defect it should only occur
> if Early Offer is enabled. Disabling Early Offer should work around it.***
> *
>
> ** **
>
> This defect, as it stands now, is only going to be fixed in 9.1(2) and
> 10.0(1) so if you wanted it in an 8.6(2) ES you would need to open a TAC
> case and request the fix be ported to the ES.****
>
> ** **
>
> +Chris****
>
> Unity Connection TME****
>
> ** **
>
> *From:* Ryan Ratliff (rratliff)
> *Sent:* Thursday, May 23, 2013 10:53 AM
> *To:* Anthony Holloway
> *Cc:* Cisco VoIP Group; Chris Ward (chrward)
>
> *Subject:* Re: [cisco-voip] DTMF Method 0****
>
> ** **
>
> 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) <[email protected]>
> 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:[email protected]] *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:[email protected]<[email protected]>
> ] *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
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ** **
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> 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/e62176a5/attachment-0001.html>
------------------------------
Message: 6
Date: Fri, 24 May 2013 09:05:46 +0200 (CEST)
From: "[email protected]" <[email protected]>
To: [email protected]
Subject: [cisco-voip] Connecting Cisco 2911 Voice Gateway to Amplified
sound system
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Guys, I have to connect the cisco voice gateway 2911 to an audio system
that serves amplified speakers located in the store customer.
customer want dial an internal DN, and speak to the employees in one way voice
using the amplified audio system.
With vic3-E&M can I accomplish the customer requirements?
I also enclose photos of the amplified sound system
Thank you for the answer.
Alessandro Bertacco
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/ffebf1ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2013-05-21 10.47.14.jpg
Type: image/jpeg
Size: 2121237 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/ffebf1ea/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2013-05-21 10.47.22.jpg
Type: image/jpeg
Size: 1817388 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130524/ffebf1ea/attachment-0001.jpg>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 115, Issue 23
*******************************************
