SMGR Error Adding a SIP User

[wpetilli]

I'm trying to add this SIP user. I've done several dozen of these today and this one is spitting back this error:
The following errors have occurred:
Endpoint "3179" on CM "US_CM" could not be associated to user "3179@blackstone.com". Cause of failure: "3584 " Use 'change' command to modify/add applications for this extension

I thought this may mean there is something with a duplicate in the system. Not seeing that anywhere. The CM station looks like all the others. Any ideas what's blocking this? I deleted the SIP user and started from scratch and it keeps happening. Just on this one.

 

[ZeroZeroOne]

I don't know "why" but sometimes there is a database mismatch between System Manager User, System Manager Endpoint, and Communication Manager Station.

Check in System Manager under Elements / Communication Manager / Endpoint / Manage Endpoint if 3179 exists.
Check in Communication Manager (ASA, PuTTY, etc) to see if station 3179 exists. My guess is that the CM station was created but System Manager does not have the Endpoint.

If the station exists in CM but not in System Manager you can try removing the station in CM then build the User again.
If the station exists in CM AND the Endpoint exists in System Manager, try building the User but check the box "use existing endpoint".
If all that fails or the station does not exist in CM, try a manual Initialization synchronization between System Manager and Communication Manager. That seems to solve a lot of weird problems. I don't know if that's the best fix, but it seems to work more often than not.

 

[wpetilli]

Station exists in CM. Using SMGR and element cut through also shows the CM station. I can add the SMGR user no problem. Clicking on 'use existing endpoint' and entering the CM extension does populate all the fields, so it is able to see it. When hitting commit I get the error. Just happened on another user as well. Since everyone is remote it's kind of hard to blow away the stations and re-create them. Need to figure out what's preventing these.

 

[ZeroZeroOne]

Are the stations already in use? The only reason I suggested deleting the CM station is that I thought this was a net-new station. If CM stations existed and you're just adding the SMGR User then obviously you don't want to delete them.

Running the synchronization with CM won't blow any stations away but will "reset" SMGR databases to what is in CM. It takes about 40 minutes, depending on station count and configuration, but really does clean things up.

Run a "save translations all" on CM first. Since you can't make any changes in SMGR while the sync is running you may want to run it after hours or at least make sure any other admin is aware.

 

[kyle555]

In CM, did off-pbx station mapping get blown away? or on the last page of the station form, did the sip trunk: field get blanked out?

 

[wpetilli]

I guess I'll try that full re-sync later. There's nothing different about these CM stations than any other I've created so far. When I click the 'use existing endpoint', it finds the CM station and does populate all those fields so not sure what it doesn't like.

 

[kyle555]

are you adding SIP profiles to H323 stations? Are you clicking the "allow dual registration" thing?

If so, blank out the off-pbx station mapping for that extension in CM and try again.

 

[wpetilli]

Yes, these are dual registrations and yes, I'm clicking that bottom field. Checked on that also.. I haven't populated that off-pbx station mapping yet. I've provisioned almost 50 of these things the same exact way and I have about 3 that are spitting out this error. Not finding the common denominator with them.

 

[wpetilli]

I attempted to create one of these folks again and got the error. The error seems to reference an extension. From the above 3584 is another SIP user. No association with this user. I deleted the 3584 user and was then able to create the problem user. I tried then next problemed user and the error popped up with another extension. This error was the extension of the admin of this specific user. I thought maybe it didn't like that the admin had bridges of this person.. I removed those and still get the error. I ran a full data sync as recommended above and that did not resolve this. I still cannot add this user.

 

[kyle555]

did your init sync complete happily?

 

[wpetilli]

Yea, I watched it go through every section of CM. Took about 20 mins or so, but completed successfully. I've literally done 50 of these in the last 2 days and I have these 3 outliers that make no sense.

 

[kyle555]

Go in logs, log settings, anything around com.avaya.iptcm.eps.logging.debug.cm and anything that would write to /var/log/Avaya/mgmt/iptcm/debug.log, set it to finest, and make it retain more files of larger size.

That'll tell you what it's really complaining about.

 

[wpetilli]

I've never touched this section so very green on this. I attached what I see in those areas. I'm changing all of them to what you reference above?

 

[kyle555]

Yeah, so the com.avaya.iptcm.eps.logging.debug.cm log appender writes log entries of ERROR or worse to /var/log/Avaya/mgmt/iptcm/debug.log


If you edit those appenders, you can make them log ALL. You'll also see the log retention - usually like 5x5MB. You can change that to 10x10MB for /var/log/Avaya/mgmt/iptcm/debug.log

Test your config, get the error, grab the log files, and put the logging config back - too many things on ALL slows down SMGR

iptcm debug.log will show you what's puking

 

[wpetilli]

I modified that specific logger and then went to attempt to create the endpoint profile again and it failed. I went back and changed back those log file settings. Now for the stupid question.. where do I find that log? I went into Log Viewer and nothing in there looks like what I'm looking for.

 

[kyle555]

winscp in that folder on SMGR

if you don't have the CLI password and your web account is "sys admin" level, click the wrench in the top right and you can enable CLI access for your web account

 

[wpetilli]

I unchecked 'allow h.323 and SIP endpoint dual registration', hit commit and it didn't error. Went back in, checked 'allow h.323 and SIP endpoint dual registration', hit commit and that was then successful. so weird