Hello, I am planning an upgrade of our UC environment this weekend. I've been in contact with Cisco Licensing support all week to get the appropriate license for all the services. For CUCM I have ran the Pre Upgrade License Utility however they keep asking me for the ELM license request. I've told them several times that ELM gets installed during the upgrade so I cannot provide the information beforehand. They've escalated my ticket to product management however i'm not sure i'll get a response before my maintenance window. Can I proceed with the upgrade of CUCM/Unity/Presence and resolve the licensing afterwards? will it run in eval mode for a while? Can someone also confirm this is the proper upgrade order? CUCM Publisher Upgrade to 9.1 Unity Publisher Upgrade to 9.1 Presence Publisher Upgrade to 9.1 CUCM Subscriber Upgrade to 9.1 Unity Subscriber Upgrade to 9.1 Presence Subscriber Upgrade to 9.1
... View more
Thanks Jamie! Step 1 that you mentioned was going to be my next plan of attack. If that doesn't work I'll move onto the next steps that you provided.
... View more
interesting enough I can't even find that menu in the web gui. I'm going to restart the CUBAC server tonight and see if it shows up, maybe thats part of the problem.
... View more
thanks, I found that one earlier as well but not really the same issue. This isn't PC specific but Extension specific. I installed the cubac software on my laptop and tried to log into the reception extension and i'm getting the same error, however I can log into my own just fine, and she can log into another just fine. I'm thinking reseting or deleting and re-adding the phone/DN might have to be the route to go but was hoping there was another resolution.
... View more
Hi, I'm having some issues with our attendant console for the receptionist. It works for a few days after some processes are restarted - by our phone support company - however after 2-3 days she is no longer to login for her particular extension. The following error is received: Error message is 172.16.55.13. invalid extension. She can still log in under any other extension - tried mine just for testing purposes. Our support company has been troubleshooting this for several MONTHS with no resolution, they applied a patch to our esx hosts this weekend that was supposed to hopefully solve the issue but it just happened again today so I want to try and resolve this myself instead of using up support hours. Does anyone have any suggestions on possible fixes?
... View more
i'm not an expert..however I happen to be troubleshooting an outgoing caller ID issue at my office so comparing that log to mine. I have a Display entry that I don't see on yours? Display i = 0xB1, 'CALLING NAME INSERTED HERE'
... View more
Thanks for the reply Javalenc. I'm going to have to look into your questions. I am fairly new to the system as it was just handed over to me a few weeks ago from our ex-IT guy. As far as I know we are using h.323 protocol on the GW's. As for blocking on the RP's, no changes have been made and I'm not sure why one day i would see the number on my cell phone and the next I wouldn't. same RP's/RL's/PRI for all calls - I don't know how to answer this one Calls to land lines seem to show the information, calls to cellular devices do not, however both are within the same calling area code. I am going to install some of the debug/logging tools and make some more test calls.
... View more
Hi everyone, first time poster on here. i'm looking for some input on an issue i've been trying to resolve. We upgraded our phone system for an old legacy system back in November. We were using 12 analog lines to handle our calls and we are now using a new Cisco system connected to two PRI's. We have two 2911 Voice Gateways, two UCS servers with all reduntant systems. We are having issues with our Caller ID on outgoing calls coming up as unknown. The issue was brought to my attention a few weeks ago so it did not start when we did the initial cutover of systems back in November. I have done quite a bit of testing. I have called various different numbers from various different desk phones in our company. Some users that I used for testing were confused as they didn't have an issue a couple weeks ago and upon testing, it came up as "Unknown". Most of these are mobile devices including my cell phone. One day my calls will show up as unknown, the next day I will see the number that is calling however we never seem to see the name anymore. However - I've been able to track down 3 analog lines for testing and all of these lines showed the Caller Name & Number. I have gone to the support company that assited us in the phone system implementation and they cannot see anything wrong with the system. I have gone to our PRI telco (Bell) and opened two tickets for them to tell me that they simply pass along the info that comes out of our system and they do not see any issues. I'm wondering what my next steps should be? Any input? I do realize a lot of wireless carriers stripe this kind of information however because it was never an issue in the past, our CEO is not accepting this as an answer and wants it resolved. Below is a quick extract of a call log for a test call I made. I have stericked out some of the information for privacy concerns. Called number '613******' Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98397 Exclusive, Channel 23 Display i = 0xB1, 'CALLER NAME' Plan:Unknown, Type:Unknown Called Party Number i = 0xA1, '613*******' Plan:ISDN, Type:National 340823: Feb 28 10:27:42.045: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x891E Channel ID i = 0xA98397 Exclusive, Channel 23 340824: Feb 28 10:27:48.045: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x891E Progress Ind i = 0x8088 - In-band info or appropriate now available 340825: Feb 28 10:27:58.093: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x891E 340826: Feb 28 10:27:58.093: %ISDN-6-CONNECT: Interface Serial0/0/0:22 is now connected to 613******* N/A
... View more