cisco-voip Digest, Vol 115, Issue 22

[cisco-voip-request]

Send cisco-voip mailing list submissions to
        cisco-voip@puck.nether.net

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
        cisco-voip-requ...@puck.nether.net

You can reach the person managing the list at
        cisco-voip-ow...@puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."


Today's Topics:

   1. Service Parameters > Always use Prime Line (Jason Aarons (AM))
   2. Re: Service Parameters > Always use Prime Line (Nate VanMaren)
   3. Re: Service Parameters > Always use Prime Line (Wes Sisk)
   4. DTMF Method 0 (Anthony Holloway)
   5. Re: DTMF Method 0 (Chris Ward (chrward))
   6. Re: DTMF Method 0 (Chris Ward (chrward))
   7. Re: Unity Connection Exchange 2013 support (Nick Kassel)
   8. Re: Unity Connection Exchange 2013 support (Chris Ward (chrward))
   9. Re: Unity Connection Exchange 2013 support (Nick Kassel)
  10. Re: Unity Connection Exchange 2013 support (Chris Ward (chrward))
  11. Re: Unity Connection Exchange 2013 support (Nick Kassel)
  12. Re: DTMF Method 0 (Ryan Ratliff)
  13. Re: DTMF Method 0 (Anthony Holloway)
  14. Re: DTMF Method 0 (Chris Ward (chrward))


----------------------------------------------------------------------

Message: 1
Date: Wed, 22 May 2013 15:13:15 -0400
From: "Jason Aarons (AM)" <jason.aar...@dimensiondata.com>
To: "cisco-voip (cisco-voip@puck.nether.net)"
        <cisco-voip@puck.nether.net>
Subject: [cisco-voip] Service Parameters > Always use Prime Line
Message-ID:
        
<4e38db0a1959b04c8c83edcf069b53ed0d34ba1...@usispclexdb01.na.didata.local>
        
Content-Type: text/plain; charset="windows-1252"

Didn't Always Use Prime Line used to be default to True?



[cid:image001.jpg@01CE56FE.E241FB60]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130522/52c12d53/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 49250 bytes
Desc: image001.jpg
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130522/52c12d53/attachment-0001.jpg>

------------------------------

Message: 2
Date: Wed, 22 May 2013 19:16:14 +0000
From: Nate VanMaren <vanmare...@ldschurch.org>
To: "Jason Aarons (AM)" <jason.aar...@dimensiondata.com>, "cisco-voip
        (cisco-voip@puck.nether.net)" <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Service Parameters > Always use Prime Line
Message-ID:
        <2f143e71016ca34c924bf4c33aef21105abfb...@w12112.ldschurch.org>
Content-Type: text/plain; charset="us-ascii"

I don't think so.

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason 
Aarons (AM)
Sent: Wednesday, May 22, 2013 1:13 PM
To: cisco-voip (cisco-voip@puck.nether.net)
Subject: [cisco-voip] Service Parameters > Always use Prime Line

Didn't Always Use Prime Line used to be default to True?



[cid:image001.jpg@01CE56EE.88F7CEF0]


 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130522/6ac57aaa/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 49250 bytes
Desc: image001.jpg
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130522/6ac57aaa/attachment-0001.jpg>

------------------------------

Message: 3
Date: Wed, 22 May 2013 15:37:57 -0400
From: Wes Sisk <ws...@cisco.com>
To: Jason Aarons (AM) <jason.aar...@dimensiondata.com>
Cc: "cisco-voip \(cisco-voip@puck.nether.net\)"
        <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Service Parameters > Always use Prime Line
Message-ID: <d1f65f1d-741f-4aad-a6a5-0ce3f4a47...@cisco.com>
Content-Type: text/plain; charset="windows-1252"

Default is False on 6.0.1 and 4.1(3)sr8. That's the oldest I have readily 
available.

-Wes

On May 22, 2013, at 3:13 PM, Jason Aarons (AM) <jason.aar...@dimensiondata.com> 
wrote:

Didn?t Always Use Prime Line used to be default to True? 
 
 
 
<image001.jpg>
_______________________________________________
cisco-voip mailing list
cisco-voip@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/20130522/91004aa0/attachment-0001.html>

------------------------------

Message: 4
Date: Wed, 22 May 2013 23:25:49 -0500
From: Anthony Holloway <avholloway+cisco-v...@gmail.com>
To: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: [cisco-voip] DTMF Method 0
Message-ID:
        <CACRCJOj4hBC=m3phaf4howoh8paxe3jhowjjtnuqwsdyeus...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130522/5accd84a/attachment-0001.html>

------------------------------

Message: 5
Date: Thu, 23 May 2013 13:49:55 +0000
From: "Chris Ward (chrward)" <chrw...@cisco.com>
To: Anthony Holloway <avholloway+cisco-v...@gmail.com>, Cisco VoIP
        Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
        <c3d1fca271936b48839e081f898e17aa300...@xmb-rcd-x13.cisco.com>
Content-Type: text/plain; charset="utf-8"

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-boun...@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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/5a6cf03e/attachment-0001.html>

------------------------------

Message: 6
Date: Thu, 23 May 2013 13:58:41 +0000
From: "Chris Ward (chrward)" <chrw...@cisco.com>
To: Anthony Holloway <avholloway+cisco-v...@gmail.com>, Cisco VoIP
        Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
        <c3d1fca271936b48839e081f898e17aa300...@xmb-rcd-x13.cisco.com>
Content-Type: text/plain; charset="utf-8"

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-boun...@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-boun...@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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/7dd177ee/attachment-0001.html>

------------------------------

Message: 7
Date: Thu, 23 May 2013 15:13:41 +0100
From: Nick Kassel <nick.kas...@btinet.bt.com>
To: "Chris Ward (chrward)" <chrw...@cisco.com>, Go0se <m...@go0se.com>,
        <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support
Message-ID:
        <7EA99F102607DF43BDF25CC68475008710801476@lhmail.btinet.local>
Content-Type: text/plain; charset="us-ascii"

Hi Chris

 

Any update on Exchange 2013 support?

 

Regards

 

Nick

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Chris Ward
(chrward)
Sent: 22 February 2013 19:16
To: Go0se; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support

 

The target for Exchange 2013 support is the end of March. Depending on
issues found and their resolutions, this could slide. So stay tuned!

 

+Chris

Unity Connection TME

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Go0se
Sent: Wednesday, February 20, 2013 7:33 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection Exchange 2013 support

 

Has anyone heard anything about when it will be supported?

 

Thanks,

Goose

 

http://atc.go0se.com

 

==================================

Help those less fortunate than you

http://www.hopegivers.org

==================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/b8f83711/attachment-0001.html>

------------------------------

Message: 8
Date: Thu, 23 May 2013 14:25:10 +0000
From: "Chris Ward (chrward)" <chrw...@cisco.com>
To: Nick Kassel <nick.kas...@btinet.bt.com>, Go0se <m...@go0se.com>,
        "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support
Message-ID:
        <c3d1fca271936b48839e081f898e17aa300...@xmb-rcd-x13.cisco.com>
Content-Type: text/plain; charset="us-ascii"

Hi Nick,

Exchange 2013 and Office 365 Wave 15 was qualified with Cisco Unity Connection 
versions 8.6.2 and 9.1.  Minor caveats have been found and are noted below.

Cisco Unity Connection 8.6.2:
*         Exchange 2013 is supported with Cisco Unity Connection 8.6.2 SU3 
(Available on 
CCO<http://software.cisco.com/download/release.html?mdfid=283819608&flowid=31849&softwareid=282074295&release=8.6(2a)SU3&relind=AVAILABLE&rellifecycle=&reltype=latest>)
*         Office 365 Wave 15 support pending fix to defect CSCug48560.
*         CSCug48560 - Synchronization issues.  Requires BU Provided ES file to 
be released in May.

Cisco Unity Connection 9.1:
*         Exchange 2013 is Supported
*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013, 
Calendaring is not working via the Telephone User Interface.
*         Office 365 Wave 15 support pending fix to defect CSCug48560.
*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013, 
Calendaring is not working via the Telephone User Interface.
*         CSCug48560 - Synchronization issues.  Requires BU Provided fix 
targeted for late May.

Known caveats are not supported by TAC until fixed in an SU or version release. 
 Cisco Unity Connection 9.1 SU is currently targeted for early this Summer.  At 
that time, we will release fixes for the known defects.


+Chris
Unity Connection TME

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com]
Sent: Thursday, May 23, 2013 10:14 AM
To: Chris Ward (chrward); Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

Hi Chris

Any update on Exchange 2013 support?

Regards

Nick

From: 
cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net> 
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Chris Ward (chrward)
Sent: 22 February 2013 19:16
To: Go0se; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support

The target for Exchange 2013 support is the end of March. Depending on issues 
found and their resolutions, this could slide. So stay tuned!

+Chris
Unity Connection TME

From: 
cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net> 
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Go0se
Sent: Wednesday, February 20, 2013 7:33 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] Unity Connection Exchange 2013 support

Has anyone heard anything about when it will be supported?

Thanks,
Goose

http://atc.go0se.com

==================================
Help those less fortunate than you
http://www.hopegivers.org
==================================

This e-mail contains BT iNet information, which may be privileged or 
confidential. It's meant only for use by the individual(s) or entity named 
above. If you are not the intended recipient, note that disclosing, copying, 
distributing or using this information is prohibited. If you have received this 
e-mail in error, please let me know immediately on the e-mail address above. 
Thank you. We monitor our e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered office: 
81 Newgate Street London EC1A 7AJ Registered in England no: 3238603
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/8f3b72ed/attachment-0001.html>

------------------------------

Message: 9
Date: Thu, 23 May 2013 15:29:10 +0100
From: Nick Kassel <nick.kas...@btinet.bt.com>
To: "Chris Ward (chrward)" <chrw...@cisco.com>, Go0se <m...@go0se.com>,
        <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support
Message-ID:
        <7EA99F102607DF43BDF25CC684750087108014ED@lhmail.btinet.local>
Content-Type: text/plain; charset="us-ascii"

Hi Chris

 

Excellent, thanks very much for the confirmation. Is this published in
any official docs yet as I could not find it in the release notes, we
will be upgrading to 9.1.1a?

 

Regards

 

Nick

 

From: Chris Ward (chrward) [mailto:chrw...@cisco.com] 
Sent: 23 May 2013 15:25
To: Nick Kassel; Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Hi Nick,

 

Exchange 2013 and Office 365 Wave 15 was qualified with Cisco Unity
Connection versions 8.6.2 and 9.1.  Minor caveats have been found and
are noted below.

 

Cisco Unity Connection 8.6.2:

*         Exchange 2013 is supported with Cisco Unity Connection 8.6.2
SU3 (Available on CCO
<http://software.cisco.com/download/release.html?mdfid=283819608&flowid=
31849&softwareid=282074295&release=8.6(2a)SU3&relind=AVAILABLE&rellifecy
cle=&reltype=latest> )

*         Office 365 Wave 15 support pending fix to defect CSCug48560.

*         CSCug48560 - Synchronization issues.  Requires BU Provided ES
file to be released in May.

 

Cisco Unity Connection 9.1:

*         Exchange 2013 is Supported   

*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013,
Calendaring is not working via the Telephone User Interface.

*         Office 365 Wave 15 support pending fix to defect CSCug48560.


*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013,
Calendaring is not working via the Telephone User Interface.

*         CSCug48560 - Synchronization issues.  Requires BU Provided fix
targeted for late May.

  

Known caveats are not supported by TAC until fixed in an SU or version
release.  Cisco Unity Connection 9.1 SU is currently targeted for early
this Summer.  At that time, we will release fixes for the known defects.


 

 

+Chris

Unity Connection TME

 

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com] 
Sent: Thursday, May 23, 2013 10:14 AM
To: Chris Ward (chrward); Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Hi Chris

 

Any update on Exchange 2013 support?

 

Regards

 

Nick

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Chris Ward
(chrward)
Sent: 22 February 2013 19:16
To: Go0se; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support

 

The target for Exchange 2013 support is the end of March. Depending on
issues found and their resolutions, this could slide. So stay tuned!

 

+Chris

Unity Connection TME

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Go0se
Sent: Wednesday, February 20, 2013 7:33 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection Exchange 2013 support

 

Has anyone heard anything about when it will be supported?

 

Thanks,

Goose

 

http://atc.go0se.com

 

==================================

Help those less fortunate than you

http://www.hopegivers.org

==================================


This e-mail contains BT iNet information, which may be privileged or
confidential. It's meant only for use by the individual(s) or entity
named above. If you are not the intended recipient, note that
disclosing, copying, distributing or using this information is
prohibited. If you have received this e-mail in error, please let me
know immediately on the e-mail address above. Thank you. We monitor our
e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered
office: 81 Newgate Street London EC1A 7AJ Registered in England no:
3238603

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/ab41053b/attachment-0001.html>

------------------------------

Message: 10
Date: Thu, 23 May 2013 14:36:56 +0000
From: "Chris Ward (chrward)" <chrw...@cisco.com>
To: Nick Kassel <nick.kas...@btinet.bt.com>, Go0se <m...@go0se.com>,
        "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support
Message-ID:
        <c3d1fca271936b48839e081f898e17aa300...@xmb-rcd-x13.cisco.com>
Content-Type: text/plain; charset="us-ascii"

Doc updates will probably all be done once we have fixes for the caveats and we 
can do it all at once.

+Chris
Unity Connection TME

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com]
Sent: Thursday, May 23, 2013 10:29 AM
To: Chris Ward (chrward); Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

Hi Chris

Excellent, thanks very much for the confirmation. Is this published in any 
official docs yet as I could not find it in the release notes, we will be 
upgrading to 9.1.1a?

Regards

Nick

From: Chris Ward (chrward) [mailto:chrw...@cisco.com]
Sent: 23 May 2013 15:25
To: Nick Kassel; Go0se; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

Hi Nick,

Exchange 2013 and Office 365 Wave 15 was qualified with Cisco Unity Connection 
versions 8.6.2 and 9.1.  Minor caveats have been found and are noted below.

Cisco Unity Connection 8.6.2:
*         Exchange 2013 is supported with Cisco Unity Connection 8.6.2 SU3 
(Available on 
CCO<http://software.cisco.com/download/release.html?mdfid=283819608&flowid=31849&softwareid=282074295&release=8.6(2a)SU3&relind=AVAILABLE&rellifecycle=&reltype=latest>)
*         Office 365 Wave 15 support pending fix to defect CSCug48560.
*         CSCug48560 - Synchronization issues.  Requires BU Provided ES file to 
be released in May.

Cisco Unity Connection 9.1:
*         Exchange 2013 is Supported
*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013, 
Calendaring is not working via the Telephone User Interface.
*         Office 365 Wave 15 support pending fix to defect CSCug48560.
*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013, 
Calendaring is not working via the Telephone User Interface.
*         CSCug48560 - Synchronization issues.  Requires BU Provided fix 
targeted for late May.

Known caveats are not supported by TAC until fixed in an SU or version release. 
 Cisco Unity Connection 9.1 SU is currently targeted for early this Summer.  At 
that time, we will release fixes for the known defects.


+Chris
Unity Connection TME

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com]
Sent: Thursday, May 23, 2013 10:14 AM
To: Chris Ward (chrward); Go0se; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

Hi Chris

Any update on Exchange 2013 support?

Regards

Nick

From: 
cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net> 
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Chris Ward (chrward)
Sent: 22 February 2013 19:16
To: Go0se; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support

The target for Exchange 2013 support is the end of March. Depending on issues 
found and their resolutions, this could slide. So stay tuned!

+Chris
Unity Connection TME

From: 
cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net> 
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Go0se
Sent: Wednesday, February 20, 2013 7:33 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] Unity Connection Exchange 2013 support

Has anyone heard anything about when it will be supported?

Thanks,
Goose

http://atc.go0se.com

==================================
Help those less fortunate than you
http://www.hopegivers.org
==================================

This e-mail contains BT iNet information, which may be privileged or 
confidential. It's meant only for use by the individual(s) or entity named 
above. If you are not the intended recipient, note that disclosing, copying, 
distributing or using this information is prohibited. If you have received this 
e-mail in error, please let me know immediately on the e-mail address above. 
Thank you. We monitor our e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered office: 
81 Newgate Street London EC1A 7AJ Registered in England no: 3238603

This e-mail contains BT iNet information, which may be privileged or 
confidential. It's meant only for use by the individual(s) or entity named 
above. If you are not the intended recipient, note that disclosing, copying, 
distributing or using this information is prohibited. If you have received this 
e-mail in error, please let me know immediately on the e-mail address above. 
Thank you. We monitor our e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered office: 
81 Newgate Street London EC1A 7AJ Registered in England no: 3238603
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/967e83ae/attachment-0001.html>

------------------------------

Message: 11
Date: Thu, 23 May 2013 15:45:57 +0100
From: Nick Kassel <nick.kas...@btinet.bt.com>
To: "Chris Ward (chrward)" <chrw...@cisco.com>, Go0se <m...@go0se.com>,
        <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support
Message-ID:
        <7EA99F102607DF43BDF25CC6847500871080157F@lhmail.btinet.local>
Content-Type: text/plain; charset="us-ascii"

Thanks Chris

 

I presume the single inbox integration is the same process as Exchange
2010 then or do you know if this has changed.

 

Regards

 

Nick

 

From: Chris Ward (chrward) [mailto:chrw...@cisco.com] 
Sent: 23 May 2013 15:37
To: Nick Kassel; Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Doc updates will probably all be done once we have fixes for the caveats
and we can do it all at once.  

 

+Chris

Unity Connection TME

 

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com] 
Sent: Thursday, May 23, 2013 10:29 AM
To: Chris Ward (chrward); Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Hi Chris

 

Excellent, thanks very much for the confirmation. Is this published in
any official docs yet as I could not find it in the release notes, we
will be upgrading to 9.1.1a?

 

Regards

 

Nick

 

From: Chris Ward (chrward) [mailto:chrw...@cisco.com] 
Sent: 23 May 2013 15:25
To: Nick Kassel; Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Hi Nick,

 

Exchange 2013 and Office 365 Wave 15 was qualified with Cisco Unity
Connection versions 8.6.2 and 9.1.  Minor caveats have been found and
are noted below.

 

Cisco Unity Connection 8.6.2:

*         Exchange 2013 is supported with Cisco Unity Connection 8.6.2
SU3 (Available on CCO
<http://software.cisco.com/download/release.html?mdfid=283819608&flowid=
31849&softwareid=282074295&release=8.6(2a)SU3&relind=AVAILABLE&rellifecy
cle=&reltype=latest> )

*         Office 365 Wave 15 support pending fix to defect CSCug48560.

*         CSCug48560 - Synchronization issues.  Requires BU Provided ES
file to be released in May.

 

Cisco Unity Connection 9.1:

*         Exchange 2013 is Supported   

*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013,
Calendaring is not working via the Telephone User Interface.

*         Office 365 Wave 15 support pending fix to defect CSCug48560.


*         Known caveat - CSCue93988 - In Office 365 & Exchange 2013,
Calendaring is not working via the Telephone User Interface.

*         CSCug48560 - Synchronization issues.  Requires BU Provided fix
targeted for late May.

  

Known caveats are not supported by TAC until fixed in an SU or version
release.  Cisco Unity Connection 9.1 SU is currently targeted for early
this Summer.  At that time, we will release fixes for the known defects.


 

 

+Chris

Unity Connection TME

 

From: Nick Kassel [mailto:nick.kas...@btinet.bt.com] 
Sent: Thursday, May 23, 2013 10:14 AM
To: Chris Ward (chrward); Go0se; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection Exchange 2013 support

 

Hi Chris

 

Any update on Exchange 2013 support?

 

Regards

 

Nick

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Chris Ward
(chrward)
Sent: 22 February 2013 19:16
To: Go0se; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection Exchange 2013 support

 

The target for Exchange 2013 support is the end of March. Depending on
issues found and their resolutions, this could slide. So stay tuned!

 

+Chris

Unity Connection TME

 

From: cisco-voip-boun...@puck.nether.net
[mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Go0se
Sent: Wednesday, February 20, 2013 7:33 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection Exchange 2013 support

 

Has anyone heard anything about when it will be supported?

 

Thanks,

Goose

 

http://atc.go0se.com

 

==================================

Help those less fortunate than you

http://www.hopegivers.org

==================================


This e-mail contains BT iNet information, which may be privileged or
confidential. It's meant only for use by the individual(s) or entity
named above. If you are not the intended recipient, note that
disclosing, copying, distributing or using this information is
prohibited. If you have received this e-mail in error, please let me
know immediately on the e-mail address above. Thank you. We monitor our
e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered
office: 81 Newgate Street London EC1A 7AJ Registered in England no:
3238603


This e-mail contains BT iNet information, which may be privileged or
confidential. It's meant only for use by the individual(s) or entity
named above. If you are not the intended recipient, note that
disclosing, copying, distributing or using this information is
prohibited. If you have received this e-mail in error, please let me
know immediately on the e-mail address above. Thank you. We monitor our
e-mail system, and may record your e-mails.

BT iNet is a trading name of BT Convergent Solutions Limited Registered
office: 81 Newgate Street London EC1A 7AJ Registered in England no:
3238603

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/33e39c3e/attachment-0001.html>

------------------------------

Message: 12
Date: Thu, 23 May 2013 10:53:17 -0400
From: Ryan Ratliff <rratl...@cisco.com>
To: Anthony Holloway <avholloway+cisco-v...@gmail.com>
Cc: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID: <d7a1384b-3d4e-457d-afc6-8a130dc20...@cisco.com>
Content-Type: text/plain; charset="windows-1252"

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) <chrw...@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-boun...@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-boun...@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@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/191dd49b/attachment-0001.html>

------------------------------

Message: 13
Date: Thu, 23 May 2013 09:53:36 -0500
From: Anthony Holloway <avholloway+cisco-v...@gmail.com>
To: "Chris Ward (chrward)" <chrw...@cisco.com>
Cc: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
        <CACRCJOhV8=vrezr0ptng9_4byxybbrauey4tyi1dyzhzyvx...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thanks for the reply Chris.  The trunk has RFC2833 set on it, and the CUCM
version is 8.6(2a).

[image: Inline image 1]

admin:show version active
Active Master Version: 8.6.2.22029-1
Active Version Installed Software Options:
No Installed Software Options Found.
admin:

The OOB/RFC2833 is interesting as this is exactly that scenario.

Thanks again.



On Thu, May 23, 2013 at 8:58 AM, Chris Ward (chrward) <chrw...@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-boun...@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-boun...@puck.nether.net<cisco-voip-boun...@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****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/2a6af7ee/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 1122 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130523/2a6af7ee/attachment-0001.png>

------------------------------

Message: 14
Date: Thu, 23 May 2013 15:11:04 +0000
From: "Chris Ward (chrward)" <chrw...@cisco.com>
To: "Ryan Ratliff (rratliff)" <rratl...@cisco.com>, Anthony Holloway
        <avholloway+cisco-v...@gmail.com>
Cc: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] DTMF Method 0
Message-ID:
        <c3d1fca271936b48839e081f898e17aa300...@xmb-rcd-x13.cisco.com>
Content-Type: text/plain; charset="us-ascii"

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) 
<chrw...@cisco.com<mailto:chrw...@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-boun...@puck.nether.net<mailto:voip-boun...@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-boun...@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@puck.nether.net<mailto:cisco-voip@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/6d798f33/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


------------------------------

End of cisco-voip Digest, Vol 115, Issue 22
*******************************************