Search this Blog

Monday, December 20, 2010

If we collect DMA File from 4.x and load onto version 8.0(2) server, will it work?

Customer has 4.X. we are going to migrate and install version 8.0(2) on new servers, (6 in total) looking at the DMA notes, the latest DMA version is for 7.(1). So If we collect DMA File from 4.x and load onto version 8.0(2) server, will it work? or do I need to be on 7.1 first and then upgrade ot version 8.0?

We assume that we only need to run DMA on the Publisher?

Tips:

There is no direct upgrade path between any 4.x CCM to CUCM 8.x as shown below;

Table 4 Supported Cisco Unified Communications Manager Upgrades for Release 8.0(x)

#

Cisco Unified Communications Manager

#

8.0(3)

#

8.0(2c)SU1

#

8.0(2c)

#

8.0(1)

#

System Version

#

8.0.3.10000-8

#

8.0.2.41900-3

#

8.0.2.40000-1

#

8.0.1.10000-40

#

Release Date

#

Jul 27 2010

#

Jul 8 2010

#

May 6 2010

#

Feb 26 2010

#

Standard Support

#

Direct upgrade:

#

8.0(2c)SU1, 8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2)

#

Direct upgrade:

#

8.0(2c), 8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2)

#

Direct upgrade:

#

8.0(2b), 8.0(2a), 8.0(2), 8.0(1), 7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2)

#

Direct upgrade:

#

7.1(3b)SU2, 7.1(3b)SU1, 7.1(3b), 7.1(3a)SU1a, 7.1(3a)SU1, 7.1(3a), 7.1(3), 7.1(2b)SU1, 7.1(2b), 7.1(2a)SU1, 7.1(2a), 7.1(2), 7.0(2a)SU3, 7.0(2a)SU2, 7.0(2a)SU1, 7.0(2a), 7.0(2), 7.0(1)SU1a, 7.0(1)SU1, 7.0(1), 6.1(5)SU1, 6.1(5), 6.1(4a)SU2, 6.1(4a), 6.1(4)SU1, 6.1(4), 6.1(3b)SU1, 6.1(3b), 6.1(3a), 6.1(3), 6.1(2)SU1a, 6.1(2)SU1, 6.1(2)






#

Direct upgrade using DMA:

#

none

#

Direct upgrade using DMA:

#

none

#

Direct upgrade using DMA:

#

none

#

Direct upgrade using DMA:

#

none

From this excellent doc , you would have to complete a "two-hop" upgrade to 6.x or 7.x as an intermediate step as you nicely noted https://supportforums.cisco.com/images/emoticons/happy.gif

FYI - many people are holding off going to CUCM 8.x due to the number of bugs.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Incoming dial peer,we have to designate that dial peer as SIP?

We are sending SIP invite to a GW. We see it is matching inbound voip dial peer.

The question is do we have to designate that dial peer as SIP?

Our understanding is if protocol is not specified, the dial peer is H.323. It turns out it works for both cases,

dial-peer voice 1 voip
session protocol sipv2
incoming called-number .and

dial-peer voice 1 voip
incoming called-number .

IOS 12.4.15T8

Is this working as designed or by accident?

Tips:

I don't think you need to configure "session protocol sipv2" on an incoming dial-peer.

The "session protocol" command mostly used for outgoing dial-peer.

From the command reference guide:

"To specify a session protocol for calls between local and remote routers using the packet network, use
the session protocol command in dial peer configuration mode. To reset to the default, use the no form of this command."

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Thursday, December 16, 2010

CM 7.1.2: Transfer problem between two CMs in different sites.Why does the call drops?

We have a problem with my CUCM solution.We have 2 CMs with version 7.1.2.20000-5 installed in . One CM is installed in the main office and the another one is installed in a remote site. There is a WAN connection between them. By the way, These CMs are not in cluster, they are independent. In the main office we have a gateway H.323 that has a E1 PRI line to PSTN. There is a connection to the PSTN only from main office, we have no connection to the PSTN from the remote site.

The problem is the following: When an extension of main office receives a call from PSTN and someone wants to transfer the call to an extension of the remote site, the phone rings but when someone lifts the handset to answer, the call drops.

We have set up a inter cluster trunk between the two CMs. Calls between IP Phones in different sites work well. The problem is when the caller is on PSTN and wants to communicate with an extension of remote site.

Tips:

The first suggestion would be to check regions/locations because between sites you may have g729 setup to save bandwidth whereas your PSTN call is probably arriving as G711.

Try checking the settings of the H323 gateway and the trunk connecting the two CUCM's to see if there is a difference, if the regions are the same, check the locations.

Other things to check are if you have 'MTP Required' checked or not and resources are available for this.

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Phone Time or timezone problem

We have two customers right now with problems with the time zone on their phones.

Customer 1:

  • 7921 CP7921G-1.3.3
  • 7940 P00308010100

Both this models display a wrong time (-1 of current time)

  • 7906 SCCP11.8-5-2SR1S

This model displays a correct time.

Customer's running CUCM 7.1.3.20000-2

NTP seems correct:

admin:utils ntp status
ntpd (pid 24900) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.1.0 LOCAL(0) 10 l 28 64 377 0.000 0.000 0.004
*X.XXX.X.XX XXX.XXX.X.XXX 3 u 642 1024 377 6.884 -9.076 3.476


synchronised to NTP server (X.XXX.X.XX) at stratum 4
time correct to within 115 ms
polling server every 1024 s

Current time in UTC is : Wed Oct 27 14:14:38 UTC 2010
Current time in Europe/Lisbon is : Wed Oct 27 15:14:38 WEST 2010
admin:

Date/Time Group is configured to (GMT) Europe/London * (Compatible with legacy phones)

Customer 2:

  • 6941 SCCP69xx.9-0-3-a

This models display a wrong time (-1 of current time)

  • 7962 SCCP42.9-0-2SR1S

This model displays a correct time.

Customer's running CUCM 7.1.5.30000-1

NTP also seems correct:

admin:utils ntp status
ntpd (pid 31403) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
127.127.1.0 LOCAL(0) 10 l 39 64 377 0.000 0.000 0.004
*XXX.XXX.XX.XX XXX.XXX.XX.XX 4 u 438 1024 377 0.526 0.797 23.508
synchronised to NTP server (XXX.XXX.XX.XX) at stratum 5
time correct to within 304 ms
polling server every 1024 s

Current time in UTC is : Wed Oct 27 14:13:56 UTC 2010
Current time in Europe/Lisbon is : Wed Oct 27 15:13:56 WEST 2010
admin:

Date/Time Group is configured to (GMT) Europe/London * (Compatible with legacy phones)

It seems to me that old legacy phones (7921, 7940) and new budget phones (69XX) seem to be affected with this problem.

We've searched online and found nothing. Did any of you had this problems?

Tips:

This is a known defect : Click here for bug details .

7940/7960/69XX phones are showing 1 hour before the real time.

The following versions are affected:
* 7.1.3: all CM versions below 007.001(003.33031.001)
* 7.1.5: all CM versions below 007.001(005.12008.001)
* 8.0.2: all CM versions below 008.000(002.41007.001), 8.0.3 shouldn't be affected.

We already have COP files for the 3 branches mentioned above:
Click here for 7.1.3
ciscocm.dst-updater.2010i-1.el4.7.1.3.cop.sgn
Click here for 7.1.5
ciscocm.dst-updater.2010i-1.el4.7.1.5.cop.sgn
Click here for 8.0
ciscocm.dst-updater.2010i-1.el4.8.0.2.cop.sgn

Please bear in mind the following suggestions when installing the COP
files:
- Installation to all machines in the cluster is required
- As with any installation or upgrade, it is recommended that you apply this Update during off peak hours.
- When applying this Package be advised that a cluster wide reboot is required.
- It is also recommended that this update be installed on all machines in the cluster before the cluster is rebooted.

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.
 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */