Share:

Replies

i was able to resolve this issue i changed the sccp adapter from the Loopback0 ip 10.1.10.2 to uses Vlan2 ip 192.168.2.2 the same subnet that the integrated-service-engine0/0 is on it registered correctly after that below are the show sccp all and the show

Thanks for the info, the story on this system is trouble some, i had worked with older pbx systems, but never an digital voip system. the owner of the company dealt with verizon on the system. and it was installed buy tele-source from pittsburg. they came in installed it and walked way, no training or support. i did have a service contract with cisco but that expired last fall. i think the original config was cli it came with cca 1.8 i didn't know how to change names on extentions or anything. i have made some changes using cme, cue, cli, and cca but as you can see there is alot of cli that is out of bounds for cca so every time i make a change using cca i have to fight to get it in line with the custom out of bounds cli. i know it would probably be better to wipe the config and start fresh with cca. i've pritty much been self taught on everything or what i have may have learned from tact support before my contract ran out. they need to write a better manual on just this system. there are alot of things i would like to utilize on the system but can't like extention mobility, using the wan with vpn for remote teleworker. but i have the issue that my data network is on one router with no vpn and voice uses the uc520 with no wan access i also have caller id issues that i need to deal with. it really is just a mess that keeps getting worse

It is always good and appreciated to get the story behind the system as it can help with providing support especially on forums or long distance

I spent more time looking over your configuration and I have to say that you would be better of remaining on a CLI basis for now, however I will put forward a recommendation for you, and I appreciate that it is a huge leap from Ad-Hoc conferencing not working to what I am going to propose but I assure you there is logic behind this

Recommendations:

Book out an entire Saturday to update your system

Make all the required prep-work well and truly before the day I.E obtain the latest Software Pack, Obtain the Latest CCA, Diagram how you want the UC-500 to sit inside the network, or if it is to sit outside of the network how you can get a valid path to it, how the call flow topology needs to work, and what rules need to be placed where, why, what and how

NOTE: Happy to give you a Visio diagram to kick start this for you, believe me when I say having it drafted up like this will make your life a million times better

Purchase a new SBCS Contract, let me assure you that the small amount of money you have to cough up for it, is well worth it, and it will cover the system, you and the organization for another 3 years, this does not just include support, but also Software Packs when released and all the associated upgrades to feature sets (This alone is worth 40% of the contracts value)

If required and you would like some guidance with the install and setup, I am happy to do the following: Make sure I am awake for the rebuild day and help you out (Australia v USA time zone), either Face time if you have an iPone or Skype if other, so we can stay in constant communications and you can show me the screen or If we can TeamViewer is an option (I don't have WebEx so out of luck there) we can do remote desktop session, but this can pose some issues.

If we can we use CCA to backup the CUE and the CME, if that does not work then we do a CLI (TXT) based backup only just to make sure we can quickly revert back if we have to, but be warned this would only be a partial reversal, it will most likely not go back to full restoration (I have to say that to prepare for it).

You should also in any event prepare yourself for the whole process to take a while, I will guesstimate the times for you now so you can try and work out if this is still a viable option for you.

Upgrade the UC-500 Software Pack (Inclusive of CUE upgrade) = 1.5 hour approx (But can happen in under 40 minutes, but in some instances it has taken 1.5 so it is best to prepare for that)

Telephony Wizard process to do the pre-build (This is about 70% of the system build) = 45-70 minutes (This is dependant on how complex the build is and what needs to be done)

CCA Applying the configuration = 30 - 90 Minutes (This is on the assumption CCA does not have heart failure, and it may... statistically speaking it has a heart attack 2 times out of every 5 builds based on my own personal observations)

Applying the last 30% of the build = 45-90 minutes (This is going to be dependant on how complex the rules and call routing will be, what features are going to be enabled, and most likely general tutoring as that will no doubt happen)

EDIT: Almost forgot the most important thing

We have to use the Bulk User Import spread sheet, this will reduce our build time down by like a country mile, it will also help ensure we get the first part and the most important part (User Details) right, if this is wrong the whole build from the word go will be wrong, something we need to avoid.

NOTE: If the UC-500 has to be integrated into the network, then 100% a Visio diagram needs to be drawn up, fully outlining the network topology, its role within the network, and all subnets and VLAN's, and in any event, unless there is critical or valid reasons to change the default VLAN ID's they will stay as defaulted by Cisco and they are as follows:

VLAN 1 = Data Vlan (This subnet can change from the 192.168.10.X to suit your current environment if required)

VLAN 90 = CUE Vlan (With the latest Software Pack and CCA, the CUE now operates within its own VLAN, Previously it was a loopback and just the subnet, well now the UC does the inter-vlan routing and I guess it is all part of the QoS process and better management of the system, not to mention it does in a sense follow proper network topology as well)

VLAN 100 = Voice VLAN (Where Possible you should always keep this @ 100 unless there is a warrant and justification to change it, pretty much all Cisco Systems Switches/Routers recognize VLAN 100 as the voice VLAN and it is their default provisioning, your Config tells me this should not be a problem)

The Default Subnets for the above listed VLAN's are as follows:

VLAN 1 = 192.168.10.X

VLAN 90 = 10.1.10.X

VLAN 100 = 10.1.1.X

VLAN 90 and VLAN 100 I would always recommend keeping them default, however if you need to change the Data VLAN to one more suitable for your network, then that is fine

Also worth mentioning, is that the UC needs to outside of the network during the build, by default it will be provisioned to do DHCP for the Data VLAN until we get in there and remove it, unless we are using CCA 3.1 which now has the ability to disable the Data VLAN DHCP.

My Experience tells me that on the day we could be in for a long 5-6 hour journey, its just not possible for me to call it a breeze setup and do it in 3 hours or under, rarely has it ever gone that smooth for me, so if you provision 4-6 hours for the rebuild, come Monday morning the organization will practically have a brand new phone system functioning, what I would hope, EXACTLY how everyone would expect it to minus any potential compromises.

A lot of info to take in there, but if you embark on it, I give you my work I will help you out where possible given the distances and time zone, but you will have help with it one way or another

First thing I noticed was that your configuration has a bit of a miss-match going on.

Just to give you an example of what a full CCA configured system would look, which may help you to get your issues sorted.

Your Config:

sccp local Loopback0

sccp ccm 192.168.2.1 identifier 1 version 4.0

sccp

CCA Config Untouched:

sccp local Vlan90

sccp ccm 10.1.1.1 identifier 1 version 4.0

sccp

NOTE: sccp local is actually pointing to the CUE VLAN in this configuration, but in particular you need to pay attention to the CCM address.

Your configuration is pointing to .2.1

and under your telephony-services your source address is:

"ip source-address 192.168.2.2 port 2000"

On My comparable configuration the CCM Address is the same as the ip source address:

"ip source-address 10.1.1.1 port 2000"

I think if you line it all up it should work... Well at least that's what I am thinking at this stage.

Is this a CLI based configuration or CCA??

Looking at the configuration it would seem that it is an older UC500 Software Pack as the latest build of CCA and Software Pack would have built it differently, so not sure if my suggesting would the right result just yet.