Fixes #11 and use semantic versioning; more documentation

Fixes #11 and use semantic versioning

• when there is monitoring, but no capture, indicate so in fritzcap.py main script
• new threading base class ExceptionLoggingThread that logs exceptions during run: all thread classes now descend from ExceptionLoggingThread
• in call_monitor, when there is no capture_monitor: prevent exceptions and ensure the intended logic still works
• semantic versioning http://semver.org/

2017-07-09 10:33:21,889 - FritzCap version 2.3.1 started.
2017-07-09 10:33:21,889 - Note: -m or --monitor_calls without -c or --capture_files does monitoring without capture.
2017-07-09 10:33:21,890 - Connect    to the call monitor service on 192.168.124.23:1012.
2017-07-09 10:33:21,897 - Connected  to the call monitor service on 192.168.124.23:1012.
2017-07-09 10:33:37,816 - Ring       (ID:0, ActiveCalls.:1, Caller:xxxxxxxxxx, DialedNumber:yyyyyyyyyy, LinePort:SIP0)
2017-07-09 10:33:43,075 - Disconnect (ID:0, ActiveCalls.:0, Caller:xxxxxxxxxx, DialedNumber:yyyyyyyyyy, LinePort:SIP0)
2017-07-09 10:33:58,084 - Connection to the call monitor service on 192.168.124.23:1012 stopped.
2017-07-09 10:33:58,084 - FritzCap version 2.3.1 finished.

More documentation

Interface keys and descriptions found on some Fritz!Box configurations

Release 2.3

new fritzcap.py version 2.3 that fixes these issues:

• #1 can capture from Fritz!Boxes other than named fritz.box
• #2 can logon to Fritz!Boxes configured for named login (not just root)
• #3 .gitignore bytecode and log files
• #4 supports Mac OS X / MacOS in addition to Linux and Windows
• #5 allows capture from non-router Fritz!Boxes by specifying --capture_interface
• #6 with --show_interface parameter to list which interfaces a Fritz!Box can capture from