CUCM BE5000 to BE6000

I'm on a journey to upgrade my current BE5000 IBM 7828 server to a virtualized environment. I currently am running version 8.6 of cm/unity. To my understanding I need to upgrade to version 9.x before making the move to BE6000. At some point I believe cm and unity split into separate products. I currently have a UCS C200 that I can use as a temporary server to perform the migration and my current VM environment has Dell PE730 servers that I want to eventually use for the UC environment. So is this the proper migration path below:
Upgrade to 9.x of BE5000
Upgrade to BE6000 (which supports virtualization) from 9.x of BE5000
I also have Presence 8.6, UCCX 8.5, and Workforce Optimization Advance Call Recording 8.5.2 that I will be upgrading as well. These products are already virtualized on my PE R730's.
I have UCSS on all of my products so I will be using the PUT tool to request the various upgrades.
As far as the licensing goes, I assume I just need to email [email protected] for the new licenses? I have already done this for my UCCX environment, (had to change primary DNS),and have not heard anything and it has been 5 days. Am I using the correct path to perform the license requests? In my opinion 5 days is way to long for this service, especially for the price I pay for UCSS and smartnets. Oh, well I'll quit ranting about that.

"my current VM environment has Dell PE730 servers that I want to eventually use for the UC environment"
First of all to be clear, since your post says you want to move to BE6k. BE6k is only supported on UCS hardware (C220/200). Its a packaged solution, contains pre-installed ESXi, pre-loaded software, UCS hardware.
You can certainly use third party servers for UC (non BE6K), but review the supported hardware specs:
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#.22Can_I_use_this_server.3F.22
For license part you are on right track, Cisco licensing team should be able to help you.
-Terry

Similar Messages

BE5000 to BE6000 License Migration

We currently have Business Edition 5000 Version 9.1 installed with 125 CUWL Standard licenses. We do not currently have UCSS or ESW. We are looking to upgrade to BE 6000 Version 10.5. Our supplier has told us that we need to purchase the BE6000 appliance 25 CUWL bundle and purchase 100 new CUWL licenses in addition to a new SWSS(UCSS+ESW) contract. We were originally looking to purchase the ESW contract but this has now been replaced by SWSS. I had originally been told that the CUWL licenses were transferable between Unified Communication applications using a zero cost migration option and that we would not need to purchase new licensing. I understand that this may only be available with active UCSS.
My question is would I be able to purchase SWSS on our existing BE 5000 v9.1 and then obtain a zero cost migration to BE 6000 9.1 and then utilise the SWSS contract to upgrade to 10.5.
Having to purchase new CUWL licensing is increasing the cost by a substantial amount.
Thanks
Colin

If you're a partner, you want to reach pre-sales for current promotions, or your SE.

Active Directory synchronization working, authentication not on CUBM BE5000 8.6(1a)

I successfully set up Active Directory synchronization between my CUCM BE5000 appliance running 8.6(1a) and our Windows 2008 Server Active Directory. Users are replicating successfully, but authentication is not working even though I am using the same LDAP manager distinguished name and password for both. I have a suspicion to the cause of this problem but for the record, the following is my relevant configuration:
System/LDAP/LDAP System:
LDAP Server Type Microsoft Active Directory iPlanet or Sun ONE LDAP Server OpenLDAP Microsoft Active Directory Application Mode
LDAP Attribute for User ID userPrincipalName sAMAccountName mail employeeNumber telephoneNumber
LDAP Server Type: Microsoft Active Directory
LDAP Attribute for User ID: userPrincipalName
System/LDAP/LDAP Directory:
LDAP Configuration Name: bgctnv.local
LDAP Manager Distinguished Name: CN=cm.sync,OU=BGCTNV Users,DC=bgctnv,DC=local
LDAP User Search Base: DC=bgctnv,DC=local
LDAP Server Information: bgctnv.local, port 389 (to query any domain controller in DNS; I have also tried specific IP addresses)
System/LDAP/LDAP Authentication:
LDAP Manager Distinguished Name: CN=cm.sync,OU=BGCTNV Users,DC=bgctnv,DC=local
LDAP User Search Base: LDAP user search base is formed using the User ID information (pre-populated, I cannot change this)
LDAP Server Information: bgctnv.local, port 3268
All of my Active Directory users are now populated and active under End Users. However, I am not able to log into /ccmuser among other things using my valid domain credentials. I am a super user as well as a standard end user.
Curiously, invalid usernames (userPrincipalName in my case) return the error "Log on failed - Invalid User ID or Password" while a valid username, with or without the correct password, returns only "Log on failed." That seems to imply that some part of the authentication or LDAP bind is taking place.
Here's the catch. The base domain here is bgctnv.local while we use bgctnv.org as a valid and acceptable alternative UPN suffix in Active Directory. Every Microsoft and every third-party program I have used will accept [email protected], but I'm beginning to think that CM will not, or is having some sort of translation issue. I read that alternative suffixes can cause problems in Active Directory forests with multiple trees, but this is a vanilla, single domain environment.
I don't even know where to look to debug this issue. Has anyone seen this before or can anyone tell me where to look for logs?
Thanks,
John

I found the following:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/directry.html
As mentioned in the section on LDAP Synchronization, in order to support synchronization with an AD forest that has multiple trees, the UserPrincipalName (UPN) attribute must be used as the user ID within Unified CM. When the user ID is the UPN, the LDAP authentication configuration page within Unified CM Administration does not allow you to enter the LDAP Search Base field, but instead it displays the note, "LDAP user search base is formed using userid information."
This may help in some situations where there are multiple trees in an AD forest, but it is definitely not the solution. Even with multiple trees, it is common to use alternative UPN suffixes. Nothing in AD requires or even recommends that you exclusively use your AD domain root as the UPN suffix.
For example, company.local may use company.com as an alternative but primary UPN suffix to provide simplicity for users. Users can then achieve more broad SSO capabilities by using their familiar email credentials when authenticating for company.local services.
When using UserPrincipalName as the LDAP synchronization attribute for the CM User ID, the configuration requires that the search base for authentication be derived from the UPN suffix, regardless of whether it is a single domain or multiple trees within a forest. This makes it impossible to authenticate by UPN unless your UPN is explicitly your root domain name. From the example above, CM would try to bind [email protected] against DC=company,DC=com instead of the correct DC=company,DC=local.
The logical solution would be to allow the administrator the option. Why not have a choice of whether to generate the user search base from the userid (UPN) information, or be able to specify the search base as well like it allows with any other synchronization attribute?
Would this be a feature request, bug report, or neither? I'd really appreciate it if Cisco considered this but I don't know the proper channel.

BE6000 CUCM 9.1 version licensing query

Hi All,
We have a BE6000 with CUCM 9.1 and UCL enhanced license subscription for 3 years. Can somebody help me understand what we need to do at the end of 3 years? Do we need to renew the licenses or do we have to purchase new licenses all together.
Thanks

Once you purchase the licenses, it stays with you and does not expire. However, if you do not keep your UCSS current and smartnet subscriptions, you will not be able to upgrade to version 10 or higher. (after three years). If you let it expire, Cisco usually has a program in place to allow the customer "get well" or "get current" for subscriptions. Instead of buying new licenses, you will be required to buy upgrades or renew your subscription at a higher price.
In a nutshell, stay current on your UCSS and SmartNet contracts and you will be fine.

CUCM 7.1 migrating to BE6000

I have a customer that is moving from their UCM 7.1 to a BE6K. The have ucss/esw and I cannot figure out how to migrate their current licenses on UCM. They are getting new hardware, so it is not a upgrade to the existing servers. Also is there a way to migrate the data from the current system into BE6K or would it be better to build it and export/import the information.
Thanks.

Hi,
We're about to refresh the BE6000 ordering guide, which includes the following on this subject.
Links for your convenience:
www.cisco.com/go/license/migration
www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_1_1/license_migration/CUCM_BK_CBF8B56A_00_cucm-license-upgrade-guide.html
Hope that helps,
Andy

How to activate 5 free UCCX bundle with CUCM in BE6000

Hi,
I'm deploying BE 6000 and am currently trying to install licenses.
I'm wondering how do we get 5 UCCX enhanced licenses that come as promo with the UCCM?
We ordered HA licenses and an additional 5 enhanced licenses (the goal is to have 10 with the ones from the promo).
I activated the HA license and the additional 5 enhanced licenses but how do I get the 5 enhanced licenses that come as promo?
Regards.

The licenses were delivered electronically.
With the BE6000 we received some envelopes with licenses for the VCS and UC hypervisor.
In the electronic licenses I see the line CCX-10-5E under R-CBE6K-K9 but we didn't get a separate PAK for the 5 free CCX licenses so that we can activate it.
Regards.

Jabber Client on Samsung S3 mini (GT-I8190) cannot register on CUCM 9.1

We have a BE6000 running with CUCM 9.1 and Desktop Phones, Windows Jabber, iPhone Jabber and iPad Jabber are all working.
Now i wanted to register a the Samsung S3 mini (GT-I8190) with Android 4.1.2 and get always the message "Connection failed." - i can ping the CUCM Server from the Phone (it's connected over AnyConnect Mobile Secure Client) and the profile seems to be configured correctly - even tried with another profile and the same error.
The Jabber IM is working fine on the device, just Jubber (Voice) is not working
Baseband version is I8190XXAMD3
Kernel version is 3.0.31-1154865
Build number is JZ054K.I8190XXAMD3

H,
yes i already did that. but when i used the same credentials on a galaxy note 2 i was able to login successfully,

How to migrate from BE6000 to Communications Manager

Dear forum members,
first of all, I'am tired. I have been on a long journey from the day we bought our Cisco Unified Communication system until now.
Technically everything worked just fine, right from the beginning until now. But starting from the first day, I had several huge
issues with our Cisco reseller (Deutsche Telekom/T-Systems).
It all started with the fact, that all hardware related contracts and services were SmartNet Services and added directly to our company account.
All software related services were booked as "Shared Services". So we were the rightfull owner of the licenses but our reseller had to migrate/issue all tickets, licensing requests and so on.
It took us (me and our reseller) over a year to set these things "right".
Right now, everything (hardware and software related services, licenses, ...) are bound to our Cisco account. We can open TAC cases, download software/firmware and so on.
Last week, we migrated successfully from Call Manager 8.6.5 to 10.0. So I was really happy to see, that everything worked fine (I could migrate my licenses, download the software, ...).
I thought, "Hey, finally eveything works as expected..."
I was wrong, so wrong...
What happend? I tell you what happend...
During the migration, we had to move all our servers (CUCM, CUC & CUPS) from our Cisco C200 M2 Server to our Dell VMware cluster, because the C200 M2 is (as far as I know) not supported anymore for BE6000 10.x and we didn't wand to buy a new C220 M3 server.
Due to the fact, that the BE6000 is only supported on that hardware, we decided to migrate our BE6000 to a Cisco Unified Communications Manager.
Our reseller told me, that Cisco Unified Communications Manager is supported on third party hardware (if the hardware meets certain requirements, like processors and so on) and due to the fact that we only use CUCM, CUC & CUPS there would be no difference for us when it comes to features.
So I said: Great, let's do that. And when you are doing that, can you please order us a license for a collab edge gateway (the thing that enables Jabber to proxy through the firewall without the need of a vpn tunnel).
And that was the point when our communication stucked...
Since that mail, I don't get any response from our reseller regarding this two tasks. They told me, that I can do that myself. I tried that and searched all cisco portals and then opended a TAC case.
The TAC team told me, that our reseller had to file a sales order (is that right?) and send me back to them.
Right now, I'am trapped between Cisco and my reseller and I'am really tired. Can someone please tell me what I can do/have to do to patch things up?
Kind regards,
René

DRS from your current server which is using the 6K OVAs, into your dell server which should NOT be using the 6K OVAS, but any of the other non-6K options you have.
I assume you've already verified your server is supported under 3rd party spec guidelines???
But, that's all it takes to move from a 6K into an enterprise CUCM, or the other way around as well.

Windows 2008 Server Co-residency BE6000/BE7000/TRCs/Specs-Based.

Hey,
I'm trying to figure out where I can run a Windows 2008 R2 server:
BE6000: seems like no based on http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/BE6000/Coresidency/9_x/BE6K_coRes.html
BE7000: the data sheet has a "Co-residency Policy" link that provides no information on co-residency. I'm assuming yes and that there is no similar list as for the BE6000.
TRCs: I assume yes
Specs-based: I assume yes.
It would be nice if this was corralled into a single location.
Thanks for any answers.

If you run 6K/7k over HYP or FND license, then yes, the above link applies to both. Not sure if you can also buy either license with TRC or spec-based TRC, if so, then they also fall under the guidelines from the link.
If you run any of the above options over VMware std, ent, or ent+ license, general co-res guidelines from virtualization wiki apply.

Moving CUCM Cluster from 7.1.5 to 10.5 and migrating P2V

Community - What I am looking for is advice from those who have actually done it! Reading about sex and having sex are two different subjects. I am finding relevant docs on the CISCO site, some are contradictory. One doc on CISCO Prime Deployment says yes to CUCM 7.1.5 and another says no. We know the standard "refresh" upgrade process, cop files and that entire drill. What we are looking for is comments from those who have done it before! Our Cluster is mixed MCS servers with CUCM PUB and SUB at Version 7.1.5. Unity/UCCX at 8.0.2 with no HA (don't ask). We want to end up with BE6000 and have UCCX in HA mode on Version 10.5 (10.6)! So what do you think, Migrate all in cluster to a common base like 9, then migrate to VM and upgrade? Or try to do it some other way.
All Comments welcome and very appreciated!

@Jamie I think we eliminated PCD as a strategy. We see this as following the usual upgrade process and assume we will be taking multiple steps. Step one would be to get all on a common version and we are thinking 8.5. At that point we could do the P2V and then upgrade to 10.5 on ESXi. We need to create some HA for Unity and UCCX, but will do that after we get to 10.5. Hopefully we can upgrade the CUCM Publisher, during which time the rest of the cluster will be operational? Put Pub back online as 8.5 and then do the subscriber. Again, we think UCCX and Unity will be operational on PUB as we upgrade SUB. Once on CUCM 8.5 we will then schedule maintenace windows to upgrade Unity and UCCX. At that point we have a cluster on 8.5 ready for P2V. We do that migration and when all are on ESXi, we do the upgrade to 10.5 and add in a HA server for UCCX and Unity. How does that sound? As we really dont want phones rebooting and downloading firmware, we will do that ahead of time, but are researching the level we should get them to before the 8.5 upgrade.
@Amn thanks for the link. We have been reading all we can on the CISCO site, and are really seeking out those who have done this and can share experience.
Thanks to all who comment.

CUCM and Avaya CS1000 SIP connection

                   Hello - looking for some help on a SIP trunk configuration between the 2 devices. Currently we are running CUCM 9.1 with Avaya Session Manager 6.3. We are having issues with the call completing from the CS 1000 to the CUCM. Below are the session traces from both the Session Manager and CUCM. The CS1000 currently has 4 digit extensions and the CUCM has 7 digit extensions. We translate the number in the Session Manager to send the 7 digits. If you could lead in the right direction I would appreciate it. WOuld this have something to do with the context coming out of Session Manager? It looks like CDP.UDP and then only the 4 digits and the CUCM needs the 7. I also attached the configurations guide used for this.
Session Manager trace:
   mil-ss-01                 CUCM 9
                       SM100                10.101.2.75             10.174.2.75
13:04:53.730 |<--OPTIONS-|           |           |           |           | (1) sip:10.5.1.30
13:04:53.731 |--200 OK-->|           |           |           |           | (1) 200 OK (OPTIONS)
13:04:53,734 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:53,734 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56.183 |--INVITE-->|           |           |           |           | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7317;phone-context=cdp.udp
13:04:56.184 |<--Trying--|           |           |           |           | (2) 100 Trying
13:04:56,185 |                  Remote host is trusted                   | Trusted
13:04:56,185 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56,186 |                Applied ingress Adaptation                 | P-Asserted-Identity=<sip:[email protected]>, Request-URI=sip:[email protected], History-Info=<sip:[email protected]>;index=1, <sip:[email protected]>;index=1.1
13:04:56,186 |                Originating Location found                 | Location: mil-cs1000m-01
13:04:56,186 |        Try routing to determine if emergency call         | Location: mil-cs1000m-01
13:04:56,186 |                Request Dial Pattern route                 | for: sip:[email protected] Location: mil-cs1000m-01
13:04:56,186 |               Dial Pattern route parameters               | URI Domain: company.com Location: mil-cs1000m-01
13:04:56,186 |                 Trying Dial Pattern route                 | Domain: company.com Location: mil-cs1000m-01
13:04:56,186 |                    Dial Pattern found                     | for: 7317 Pattern: 7317
13:04:56,186 |                    Route Policy found                     | Pattern: 7317 RoutePolicyList: to_CUCM9
13:04:56,187 |                        Route found                        | for: sip:[email protected] SIPEntity: CUCM 9
13:04:56,187 |                     Entity Link found                     | SIPEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP, biDirId=null, deny=false:5060
13:04:56,187 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,188 |                 Applied egress Adaptation                 | NoAdaptationModuleExists=true, Request-URI=sip:[email protected];routeinfo=0-0, Remote-Party-ID=<sip:[email protected]>;party=calling;screen=no;privacy=off,
13:04:56,188 |                    Routing SIP request                    | SipEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP:5060
13:04:56,189 |              No hostname resolution required              | Routing to: sip:10.5.131.12;transport=tcp;lr;phase=terminating
13:04:56.191 |           |--INVITE-->|           |           |           | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7657317 P:terminating
13:04:56.196 |           |<--Trying--|           |           |           | (2) 100 Trying
13:04:56.198 |           |<--Not Fou-|           |           |           | (2) 404 Not Found
13:04:56.199 |           |----ACK--->|           |           |           | (2) sip:[email protected]
13:04:56,200 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,201 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,201 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56.202 |<--Not Fou-|           |           |           |           | (2) 404 Not Found
13:04:56.203 |----ACK--->|           |           |           |           | (2) sip:7317
13:05:07,597 |                Remote host is not trusted                 | Host not trusted
13:05:07,597 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:12.657 |           |<--------OPTIONS-------|           |           | (3) sip:10.5.2.51
13:05:12,659 |                Remote host is not trusted                 | Host not trusted
13:05:12,659 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:12.660 |           |--------200 OK-------->|           |           | (3) 200 OK (OPTIONS)
13:05:16.877 |           |<--------------OPTIONS-------------|           | (4) sip:10.5.2.51
13:05:16,879 |                  Remote host is trusted                   | Trusted
13:05:16,879 |                    Request Adaptation                     | Adapter: mil-ss-01
13:05:16,879 |                Applied ingress Adaptation                 | P-Asserted-Identity=<sip:[email protected]>
13:05:16,879 |                Originating Location found                 | Location: sas-cs1000e-01
13:05:16.880 |           |--------------200 OK-------------->|           | (4) 200 OK (OPTIONS)
13:05:24.463 |           |<--------------------OPTIONS-------------------| (5) sip:10.5.2.51
13:05:24,465 |                Remote host is not trusted                 | Host not trusted
13:05:24,465 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:24.466 |           |--------------------200 OK-------------------->| (5) 200 OK (OPTIONS)
CUCM Trace Invite:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 3188 bytes:
[1179,NET]
INVITE sip:[email protected] SIP/2.0
P-AV-Message-Id: 1_1
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
History-Info: <sip:[email protected]>;index=1, <sip:[email protected]>;index=1.1
Remote-Party-ID: <sip:[email protected]>;party=calling;screen=no;privacy=off
Allow: INVITE, ACK, BYE, REGISTER, REFER, NOTIFY, CANCEL, PRACK, OPTIONS, INFO, SUBSCRIBE, UPDATE
Contact: <sip:00000000;[email protected]:5060;maddr=10.5.1.30;transport=tcp;user=phone;gsid=68cac530-5d21-11e3-8b45-78e3b505dc88>
Alert-Info: <cid:[email protected]>
Supported: 100rel, x-nortel-sipvc, replaces
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
Via: SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140
Via: SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
Record-Route: <sip:[email protected];transport=tcp;lr>
Record-Route: <sip:10.5.2.50:15060;transport=tcp;ibmsid=local.1372169047609_2400497_2400521;lr>
Record-Route: <sip:[email protected];transport=tcp;lr>
P-Charging-Vector: icid-value="68cac530-5d21-11e3-8b45-78e3b505dc88"
User-Agent: Nortel CS1000 SIP GW release_7.0 version_linux-6.50.00 AVAYA-SM-6.3.1.0.631004
P-Asserted-Identity: <sip:[email protected]>
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
Max-Forwards: 66
CSeq: 1 INVITE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 1063
Av-Global-Session-ID: 68cac530-5d21-11e3-8b45-78e3b505dc88
P-Location: SM;origlocname="mil-cs1000m-01";origsiglocname="mil-cs1000m-01";origmedialocname="mil-cs1000m-01";termlocname="Cisco BE6K";termsiglocname="Cisco BE6K";smaccounting="true"
--unique-boundary-1
Content-Type: application/sdp
SDP Message
====================================================
v=0
o=- 746 1 IN IP4 10.5.1.30
s=-
c=IN IP4 10.5.1.36
t=0 0
m=audio 5234 RTP/AVP 18 0 8 101 111
c=IN IP4 10.5.1.36
a=tcap:1 RTP/SAVP
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=pcfg:1 t=1
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
0500bc05
0107130081900000a200
09090f00e9a4830001004000
1315070011fa0f00a10d02010102020100cc040000c56000
1e0403008183
4a1c0100180001001a011404000067353505000004000000000048710000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
011201
3c:4a:92:f4:84:f4
--unique-boundary-1--
CUCM Trying Message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:[email protected] SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
CUCM not found message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
CUCM ACK message:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:[email protected] SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
Thanks.

This document worked for us between CUCM BE6000 ver 9.0 and the Avaya.
The main focus on the Cisco side is this: Page 37 - 41
5.4. Define SIP Trunk Security Profile
Expand System  Security Profile and select SIP Trunk Security Profile. Click to
configure a SIP Trunk Security Profile.
Enter the following values and use defaults for remaining fields:
 Name Enter name
 Description Enter a brief description
 Incoming Transport Type Verify “TCP+UDP” is selected
 Outgoing Transport Type Verify “TCP” is selected
 Accept Out-of-Dialog REFER Enter
 Accept Unsolicited Notification Enter
 Accept Replaces Header Enter
Click . The screen below shows SIP Trunk Security Profile for the sample configuration
5.5. Define SIP Profile
Expand Device  Device Settings and select SIP Profile. Click to configure a SIP
Profile.
Under SIP Profile Information section, enter the following values and use defaults for
remaining fields:
 Name Enter name
 Description Enter a brief description
 Default MTP Telephony Event Payload Type Enter “120”
 Disable Early Media on 180 Enter
Note: Disabling Early Media allows local ringback to be used.
Under Parameters used in Phone section, scroll to end of section and enter the following values
and use defaults for remaining fields:
 RFC 2543 Hold Enter
Click . The screen below shows SIP Profile for the sample configuration.

BE on MCS v7 migrate to BE6000 on UCS

I have a client who has a 100 single MCS server based Business edition running version 7. Currently they are covered under UCCS/ESW nearing the end of this 3 year agreement.
What is the correct migration path to take them from V7 to BE6k on UCS. Looking possibly to add some redundancy.
Customer has CUCM/Unity Connection/Presence/Attendant Console applications.
From the SE session I believe I could
buy 2 50 or 100 user bundles or buy 1 bundle and a
migration bundle for the redundant server with all the software preloaded.
If I purchase 2 50s, this gives the active publisher a total of 100 users during normal operation?
My question is is the migration bundle a deep discounted sku that acknowledges the investment of the existing BE version 7 and MCS hardware, or do I have to go through the technology migration path to get value for the existing hardware and licenses?
Is this even the correct roadmap, from v7 or do I have to first upgrade to v9 on the existing hardware under the UCCS support terms, THEN migrate to UCS hardware?
Thank you.
md

You have mulitple options.
1. AS you described in the question, buy two 50 bundles will let you have a publisher with 100 user license, and a subscriber server.
2. Just buy one starter bundle, and use the MCS server as you back server. Please check the MCS server is supported in 9.0. In this case, you will need to upgrade the MCS server with 9.0 SW.
The migration program includes mulitples parts:
1. Migration bundle is discounted with its price just around $1K higher than the listed bare metal server price. and with pre-loaded OS and VMware. It also comes with the free VCS licesnse (5 travelsal license + 10 non travesal ), 5 CC agent license and required VMware license.
2. Don't need to purchase new license. Just migrate them. What really matters is the migration discount on license. With the 9X3 migration promotion, you can migrate you licesnse to BE6000 for $9 per license if 3 year UCSS is purchased.
3. Use the MCS server as reducndancy server or run other applications.
4. You don;t nee to upgrade to 9.0 first ro be able to migrate.
We are going to publish a white paper for migration ery soon. Please stay tuned.

Mixing BE6000 UCS Server and "normal" UCS server in the same deployment

Hello,
I have been handed a project which has one high density BE6000 UCS server and a separate UCS C220 M3 server. The latter server was included to host a MediaSense call recording system but this will only use 2 of the available 8 vCPUs on the UCS C220 M3 server.
The total number of users is 200.
I want to implement a resilient system and so would like deploy two servers in a cluster for each of the following applications:
CUCM 10.5
Unity Connection 10.5
IM & Presence 10.5
As well as these applications there will be UCCX 10.6 and Cisco Unified Attendant Console Advanced (10.5) but these will be deployed as single servers.
Looking at the UCS servers they have capacity for me to split the CUCM/CUC/IMP clusters between them.
I cannot see any technical reason why this will not work but do not want to be caught by any Cisco support policies.
If I were to implement the system in this way would there be any issues with the deployment or getting support from TAC.
The separate UCS C220 M3 server has 8 x 8GB RAM (64 total) and 8 x 300GB HDD plus a quad Ethernet card.

James first of all I am not sure I understand your query in detail. Do you mean you have two UCS220 M3 servers? and one of them is currently running BE6000?
Having said that, the key here is to carefully plan your deployment against the capacity of the servers you have,.
Eg..Deploying 200 Users, using the ff OVA
UCS 220 M3 server 1: (using default TRC ie 8vCPU with 8GB per vCPU)
Publisher (2500 cucm OVA): 1vCPU (6GB RAM), 80GB HD
IMP-Publisher (1,000 OVA) :1vCPU(2GB RAM), 80GB HD
CUC-publisher (1,000 users OVA) :2vCPU(6GB)--NB 1vCPU is reserved for ESXI, 160GB HD
UCCX-Master: (300 agent OVA): 2 vCPU (8GB) and 292GB HDD
With this placement you have a total of 22GB RAM and 612HDD used up
A break down is shown below..
Server
Server Name
C220 M3S TRC#1 (Medium)
C220 M3S TRC#1 (Medium)
Application Short Name
Application Long Name
Release
VM Name
vCPU
vRAM
vDisk
CUCM
Unified Communications Manager Release
10.x
CallCtrl: 2,500 users
1
4
80
IM&P
IM & Presence Release
10.x
1,000 users
1
2
80
CUC
Unity Connection Release
10.0
1,000 users
1
4
160
ESXi
Unity Connection
ESXi
1*
CUCCX
Cisco Unified Contact Center Express / Unified IP IVR Release
10.x
Main: 300 agents
2
8
292
ESXi
VMware vSphere ESXi
5.5
4**
* Note: This is a 1 physical CPU core per host regardless of the number of Cisco Unity Connection (CUC) VMs.
** Note: This is 4GB physical RAM per host.

Stripe Size for BE6000 RAID 10 Configuration.

Hey,
What should the stripe size be for the BE6000 RAID configuration should you have to rebuild the volume? When we got a BE6000 and looked the Stripe size seemed to be set to 64K, but I see documentation saying that 128K is what should be used (although that seems to refer to the RAID 5 configurations).
Anyone know?
Thanks,
Joey

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/virtual/CUCM_BK_CF3D71B4_00_cucm_virtual_servers/CUCM_BK_CF3D71B4_00_cucm_virtual_servers_chapter_010.html doesn't make it seem like it only applies to RAID 5.

Sharing data stores between BE6000 UCS Servers

Hi,
I have two UCS C220 M3 servers running Business Edition version 9.1.
The servers are in the same data centre and each host a CUCM server, Unity Connection server and Presence Server.
This is great as each application has two servers and so there is survivability it the case that one UCS server fails.
Now the customer wants an Attendant Console and has purchased the Cisco Unified Business Attendant Console which does not have a high availability option.
I have installed this on one UCS server where it is running happily. To provide some resilience what I am considering is turning off the CUBAC VM, copying its files to the other UCS server and adding it to the inventory of that server.
I have tested this by manually copying the files to my PC then uploading them to the second UCS server and it worked ok but took a fair time.
I was wondering if there are any ways to improve/automate this.
My first thought was whether it is possible to share the internal storage of the UCS servers with each other using some clever storage tricks (iSCSI, NFS?).
If not is it supported/recommended to add external storage (say a NAS) to the BE6000 servers and use this as a shared storage area?
If yes to the above is there a way to automate the shutdown, copying and restart of the CUBAC virtual machine on the first UCS server?
My other concern is about leaving a Windows Server VM powered off for an extended period. Is this a very bad thing as it will miss updates or is it something that Windows will deal with gracefully?
I realise that this is a bit wacky and a far better solution would have been to buy an Attendant Console with high availability built in to it.
Thanks

Guys,
Thanks for the responses.
I know what I am asking is far from ideal but this is the position that I have been put in by circumstances.
If I had been involved in the selection of the console CUBAC would not have been selected and I would not be in this position (I would probably have used Fidelus console with queuing provided by CUCM hunt groups).
Unfortunately I have to play the hand I have been dealt hence my questions about sharing data stores etc.
I acknowledge that I am stepping away from best practice but if anyone has input on my original questions I would be grateful.
Thanks
James

CUCM BE5000 to BE6000

Similar Messages

Maybe you are looking for