[cisco-voip] CSCsb57445 Can't use DPA 7630 /Octel with CallManager 5x/6x

[Jason Aarons (US)]

I attached the RSS notice, but is CSCsg21994

 

 

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method
=fetchBugDetails&bugId=CSCsg21994

 

From: Chris Ward [mailto:chrward at cisco.com] 
Sent: Thursday, October 30, 2008 4:40 PM
To: Jason Aarons (US); cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CSCsb57445 Can't use DPA 7630 /Octel with
CallManager 5x/6x

 

Jason,

You may have copied the wrong bug. This one has to do with a calledparty
field in a sccp message that is resolved in 5.0.1.

Can you check the bug ID and post back?

Chris Ward 

________________________________

From: "Jason Aarons (US)" <jason.aarons at us.didata.com>
Date: Thu, 30 Oct 2008 16:32:05 -0400
To: <cisco-voip at puck.nether.net>
Subject: [cisco-voip] CSCsb57445 Can't use DPA 7630 /Octel with
CallManager 5x/6x

Do I understand this correctly, that CallManager 4x deployments with a
DPA can't upgrade to 5x/6x at this time?  Is a hotfix available for 6x?
Will the DMA or upgrade assistant warn this upgrade will have issues?
 
 
 
DPA sends CalledPartyNumber instead of OriginalCalledPartyNumber to VM  
Symptom:
 
Calls routed to voicemail via DPA will show up in Octel destined to the
wrong voicemailbox.
This can result in the caller being prompted to login or simply getting
the default greeting.
 
Conditions:
DPA voicemail integration with CM 4.2(1) or later (including CM 5.0). 
 
Workaround:
None
 
Further Problem Description:
In previous versions of CallManager the SCCP CallInfo message sent to a
phone had the originalCalledParty and calledPartyNumbers with the same
value (that of the originalCalledParty number). This was done to be
backwards compatible with old voicemail products such as UOne. Since
this message is only used to present display information to the SCCP
device it did not impact the routing of calls.
 
CSCsb57445 was filed to fix this issue and get the calledPartyNumber to
display the correct value. This fix had the side-effect of causing the
wrong number to be sent by the DPA as the called party number.
 

________________________________


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




-----------------------------------------
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081030/376f76c0/attachment-0001.html>
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: DPA sends CalledPartyNumber instead of OriginalCalledPartyNumber to
	VM , Fixed CSCsg21994
Date: Mon, 20 Oct 2008 11:00:56 -0400
Size: 4040
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081030/376f76c0/attachment-0001.mht>