traceSM session shows no SIP Traffic

[janaya]

I am trying to run traceSM on the session manager. I get in, start and select SIP traffic. When I press enter, there is nothing displayed on the screen. If I go back and select TLS Handshake it shows data. Is there something that has stopped on the Session Manager that would permit it to display the messages? I know SIP calls are working because, well, they are working. Just not displaying in the traceSM.

Any help is always appreciated

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/

 

[kyle555]

reboot?

release?

did certs expire?

 

[bignose21]

is there a filter configured? Maybe select filter and just clear it you should at least be seeing the option messages

 

[janaya]

Release 7.0.1.2

Have not rebooted.

Tried the filter item, but that did not work.

I may have to restart them, but everything is working, just the SIP messages aren't showing in traceSM. Opened a ticket to see if there is a service that can be restarted rather than reboot. We have a lot of traffic as we are a global SIP system.

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/

 

[Wanebo]

Try clearing the buffer. If that doesn't help then tcpdump has probably dumped out or locked up and you should consider having Avaya check it out.

 

[kyle555]

if you have a lot of traffic, get another session manager

 

[janaya]

Ok. Just wanted to add the solution here.

When you ran ls -ltr on the file location, it showed that the owner of the tracer.asset.log file had changed. How or why it changed, I do not know and the tracer audit log did not show how/why it changed.

If you run into this you can change the ownership back to root/suser

-rw-rw---- 1 XXXX YYYY 5111002 Apr 30 11:30 tracer_asset.log <-- XXXX/YYYY should be the users that have RW privileges to this file. This is the file that is created during a traceSM.

To change the user

chown root:susers tracer_asset.log <-- this changes back to root/suser

If the rights have changed you need to change what type of modification is allowed by the user

chmod 660 tracer_asset.log <--This changes the RW privileges

When you run these two commands, you need to restart the rsyslog service

#service rsyslog restart <-- run to restart the service

None of these changes are service impacting.

After this was done, it all started working again.

Hope this helps the next guy.



John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/

 

[Wanebo]

Thanks for the update John!