Simple chord shapes for 4 string bass
closed and open positions
R = root
G |---|---|---|-X-|---|---| M7
D |---|-X-|---|---|---|---|
A |---|---|-R-|---|---|---|
E |---|---|---|---|---|---|
G |---|---|-X-|---|---|---| 7
D |---|-X-|---|---|---|---|
A |---|---|-R-|---|---|---|
E |---|---|---|---|---|---|
G |---|---|-X-|---|---|---| m7
D |-X-|---|---|---|---|---|
A |---|---|-R-|---|---|---|
E |---|---|---|---|---|---|
G |---|---|-X-|---|---|---| m7b5
D |---|---|---|-X-|---|---|
A |---|---|-R-|---|---|---|
E |---|---|---|---|---|---|
G |---|-X-|---|---|---|---| dim
D |---|---|---|-X-|---|---|
A |---|---|-R-|---|---|---|
E |---|---|---|---|---|---|
G |---|---|---|-X-|---|---| M7
D |---|---|---|-X-|---|---|
A |---|---|---|---|---|---|
E |---|---|-R-|---|---|---|
G |---|---|---|-X-|---|---| 7
D |---|---|-X-|---|---|---|
A |---|---|---|---|---|---|
E |---|---|-R-|---|---|---|
G |---|---|-X-|---|---|---| m7
D |---|---|-X-|---|---|---|
A |---|---|---|---|---|---|
E |---|---|-R-|---|---|---|
G |---|---|---|---|---|---| m7b5
D |---|---|-X-|---|---|---|
A |---|---|---|-X-|---|---|
E |---|---|-R-|---|---|---|
G |---|---|-X-|---|---|---| dim
D |---|-X-|---|---|---|---|
A |---|---|---|---|---|---|
E |---|---|-R-|---|---|---|
Diary of technical happenstance, simple Internet accessible scratchpad, and brain dump to save myself later
Saturday, November 24, 2018
Monday, August 20, 2018
Cisco PCD Prime Collaboration Deployment notes
User to upload bottable ISO images to PCD is adminsftp.
The password is the same as the administrator password you set during the PCD install.
If you are performing a migration, you upload the bootable images to the PCD fresh_install folder.
Filezilla works nicely as the client for the upload purposes.
SFTP typically runs on port 22.
The password is the same as the administrator password you set during the PCD install.
If you are performing a migration, you upload the bootable images to the PCD fresh_install folder.
Filezilla works nicely as the client for the upload purposes.
SFTP typically runs on port 22.
Get the PCD install logs with file get install /*
Get the PCD application logs with file get activelog tomcat/logs/ucmap/log4j/*
During migrations, existing firmware files are migrated to the new servers.
During migrations, existing wallpaper files are migrated to the new servers.
After recently migrating a CUCM cluster from 10.5 to 11.5 using PCD 11.5.1.15900-18 I found the newly issued version 11 licensing showing as "Unrecognized License Type" after synchronization. Ultimately the PLM license definition file needed to be upgraded. Although the description sounds wrong, I found you can use the license-def-11-for-PLM-10x.def file found on Cisco's Prime License Manager 10.0 download page. There is no file published specifically for PLM 11 that I could find.
Get the PCD application logs with file get activelog tomcat/logs/ucmap/log4j/*
During migrations, existing firmware files are migrated to the new servers.
During migrations, existing wallpaper files are migrated to the new servers.
After recently migrating a CUCM cluster from 10.5 to 11.5 using PCD 11.5.1.15900-18 I found the newly issued version 11 licensing showing as "Unrecognized License Type" after synchronization. Ultimately the PLM license definition file needed to be upgraded. Although the description sounds wrong, I found you can use the license-def-11-for-PLM-10x.def file found on Cisco's Prime License Manager 10.0 download page. There is no file published specifically for PLM 11 that I could find.
Monday, July 02, 2018
CUCM 12 Self Provisioning User Experience
Video simply shows the self provisioning audio prompt and real time migration from auto registration to provisioned endpoint.
Here the Cisco 8841 is registered to a RTP data center based dCloud CUCM 12 cluster over VPN setup by Cisco 1841 router over Spectrum 10/100 cable internet.
Wednesday, June 27, 2018
Webex Teams / Spark notes
From a Webex Teams / Spark client you can call other non-Webex Teams / Spark devices without hybrid services. Prefix the normal SIP URI with SIP: See below:
Webex Teams / Spark clients can be reached from other SIP based clients as well. From a device capable of dialing SIP URIs other than Webex Teams / Spark, you can reach Webex Teams clients by dialing in the format <user>@<company>.call.ciscospark.com. For eaxmaple, webmaxtor@webmaxtorcompany.call.ciscospark.com.
To clear the cache for Cisco Webex Teams on Windows:
- Sign out of the Cisco Webex Teams client.
- Press Ctrl + Alt + Del on your keyboard, then select Task Manager.
- Under the Apps tab, right-click on Cisco Webex Teams, then select End Task.
- Right-click on the Windows (Start) button, and select Run. In the Open text box, enter %USERPROFILE%\AppData\Local\CiscoSpark.
- Delete all data in the CiscoSpark folder.
Tuesday, May 22, 2018
Cisco Mobile Expert Remote Notes
Information circa Cisco Moible Expert Remote version 11.6 / May 2018
URLs:
Use a sample web app to accept calls and eliminate other variables. Authenticate to REAS locally (default local user / password is agent1 / agent1) to keep it simple. The cluster name should be your REAS server(s):
https://Cluster IP or FQDN:8443/expertassist/agent
Use a sample web app to generate calls and eliminate other variables. The cluster name should be your REAS server(s):
https://Cluster IP or FQDN:8443/assistsample
If tests using the local user are good, you can extend the test calls to your CUBE or CUCM using the same test web interface:
https://Cluster IP or FQDN:8443/assistsample?agent=sip:1234@10.10.10.10
The general administration page is here (the cluster name should be your REAS server):
https://Cluster IP or FQDN:8443/web_plugin_framework/webcontroller
The REAS Management Console is here:
https://Cluster IP or FQDN:9990
Videos from 10.6 versions showing basic configuration techniques. These appear they may have come from Cafex and the OVA deployment and WebRTC examples are no longer valid:
https://communities.cisco.com/docs/DOC-59078
The Cisco REM troubleshooting doc wiki is incomplete. More complete instructions including updated / accurate CLI can be found here:
https://support.cafex.com/hc/en-us/articles/208247075-Collecting-logs-for-Cisco-REM
Notes:
SSH to REAS(s) with rem-ssh user and run service reas status to verify reas is running.
SSH to REMB(s) with rem-ssh user and run service media_broker status to verify remb is running.
Install latest ES releases before troubleshooting regardless of release notes.
Logs are at ./opt/cisco/11.6.1.10000-7/REAS/domain/servers/appserver-YOUR_REAS_HOSTNAME/log/
The log capture script can now be run like so: ./opt/cisco/11.6.1.10000-7/REAS/bin/logcapture.sh -c -f YOUR_FILE_NAME.tar
URLs:
Use a sample web app to accept calls and eliminate other variables. Authenticate to REAS locally (default local user / password is agent1 / agent1) to keep it simple. The cluster name should be your REAS server(s):
https://Cluster IP or FQDN:8443/expertassist/agent
Use a sample web app to generate calls and eliminate other variables. The cluster name should be your REAS server(s):
https://Cluster IP or FQDN:8443/assistsample
If tests using the local user are good, you can extend the test calls to your CUBE or CUCM using the same test web interface:
https://Cluster IP or FQDN:8443/assistsample?agent=sip:1234@10.10.10.10
The general administration page is here (the cluster name should be your REAS server):
https://Cluster IP or FQDN:8443/web_plugin_framework/webcontroller
The REAS Management Console is here:
https://Cluster IP or FQDN:9990
Videos from 10.6 versions showing basic configuration techniques. These appear they may have come from Cafex and the OVA deployment and WebRTC examples are no longer valid:
https://communities.cisco.com/docs/DOC-59078
The Cisco REM troubleshooting doc wiki is incomplete. More complete instructions including updated / accurate CLI can be found here:
https://support.cafex.com/hc/en-us/articles/208247075-Collecting-logs-for-Cisco-REM
Notes:
SSH to REAS(s) with rem-ssh user and run service reas status to verify reas is running.
SSH to REMB(s) with rem-ssh user and run service media_broker status to verify remb is running.
Install latest ES releases before troubleshooting regardless of release notes.
Logs are at ./opt/cisco/11.6.1.10000-7/REAS/domain/servers/appserver-YOUR_REAS_HOSTNAME/log/
The log capture script can now be run like so: ./opt/cisco/11.6.1.10000-7/REAS/bin/logcapture.sh -c -f YOUR_FILE_NAME.tar
Subscribe to:
Posts (Atom)

