Help with MBG SIP traces – Wireshark display filters

I dont’t know why i didnt research this before but you can look for calls by the CLI using the wireshark display filters

  • show SIP packets to/from this number: sip contains 01684595000
  • show SIP packets to this number: sip.To contains 01684595000
  • show SIP packets from this number: sip.From contains 01684595000

So instead of serching through an endless list of calls for the one you are looking for

Continue reading

Micollab Deployment test mcdiagnostics.easydeploy.net

When running a diagnostic test on the deployment profile it does three tests. The third test is checking for connection from 85.214.114.20X to your micollab server on TCP port 36008 (through your MBG web proxy possibly)

You can test this manually via web browsing to this URL: https://mcdiagnostics.easydeploy.net/ucawebsocket/?ucahost=The FQDN of the Micollab server

e.g. https://mcdiagnostics.easydeploy.net/ucawebsocket/?ucahost=micollab.pmhaynes.co.uk

The web page should show “{“msg”:”(200 OK)”}” Anything else means the connection is blocked

e.g “Incomplete response received from application” is a response i got when the port was blocked by the firewall

How to :Filter wireshark by time frame

You know the score. You leave a wireshark trace running for an hour and it grows to a couple of GB. When you try and open the file it takes for ever to load and filter.

What do you do?

Continue reading

MBG : How to remove “revoked” certificates

Although i dont believe it does any harm i have wanted to remove the revoked certifcates from the certifcate management web page on the MBG

As you see above i have already removed mine

To do this simple find the revoked PEM files under

/home/e-smith/certmgmt/revoked

If you want to be specific you can search for the actual file or just delete all in the “revoked” folder

You can either access this folder with putty or via Winscp

If you dont know how to access the MBG via putty see my post here

Web proxy troubleshooting. Logs to check.

The logs to check when accessing the AWV through a web proxy are located on the web proxy MBG

/var/logs/httpd/access_log

and

/var/logs/httpd/error_log

The best way to watch them as you perform a test connection is using the “tail -f” command in putty or from the console

If you dont know how to putty to see the mbg console check out this post

Example:

tail -f /var/log/httpd/error_log |grep {your ip address you are connecting from}

and

tail -f /var/log/httpd/access_log |grep {your ip address you are connecting from}

MSL port query commands, web proxy etc

Run these commands from putty or the console. Login as root not admin

Dont know how to putty to the MSL/MBG/Micollab? See this post

nc -vz {AWV URL} 443
nc -vz {AWV URL} 4443
nc -vz {AWV 2nd URL} 443
nc -vz {AWV 2nd URL} 4443

URL will be the Micllab FQDN and the AWV FQDN

E.G. conference.yourdomain.com and conference1.yourdomain.com

When the command is ran you should get a “succedded” back