Items discussed:
Core topology with redundant, private-IP machines, both of which are behind
the SBC. SIP service psu.edu points to the SBC (firewall).
A plan for a second SBC to provide failover in the event of a single
firewall failure.
Phase 1 is PSU IB-wide,
userID to userID and all users will expect service continuity
when compared to UP. Or do we strictly adhere to the written Phase 1
definition.
We are at the point where we need to re-create the voip.psu.edu server front end to
provide AAA of the SoftPhone user. The next steps of the process is to
generate a strong SIP password to be cut and pasted by the authenticated
user into their soft client.
Complete the 15 steps for a new service creation.
Review Asterisk clustering as an option for this or the second phase.
Future meetings:
Review timelines found on \NPI\SoftPhone Versions\Soft Phone Version Control
Document
Help desk involvement -- would we consider a wiki-based support function for
Phase 1.
SNMP logging and developing maintenance / support functionality
SBC configuration overview
SIP trunk for Phase 2 reviewed