Show description

Many of these can be found in RFC-3261; however, there are additional RFCs posted on the IETF site explaining these responses. WRAPPING UP As we can see, the SIP protocol is very robust and there is a large amount of data available on how this protocol should react within our environments. While, as with many protocols, various vendors will implement this protocol in a slightly different manner. We have only discussed the basic primary stand implementation as outlined within IETF’s RFCs. Some vendors will take some liberties to lock you into their solution, as their hardware and software endpoints may not be compatible with other vendor’s products.

Another key thing to remember is that this list should be all-inclusive and it should be revisited on a regular basis. If employees are required to make long distance or international calls, the facility should be made available only to the end user who truly needs these features. Additionally, the dial plan should be configured in such a way that it requires some form of PIN for these callers prior to allowing for these long distance and international calls. This will protect against the cleaning staff dialing home in the middle of the night or malicious attacks from reselling minutes on our dime.

Baseline It is important to realize that a baseline for any implementation should be established. This provides a means to compare where the system is to where Conclusion it should be. Additionally, this could become a checklist for action items that must be performed as part of any rollout or implementation. The VoIP implementation is not exempt from these kinds of requirements. Thus, as part of the implementation, it is important to document the requirements for your deployment, with many of the aforementioned configurations in mind, to ensure your process meets all requirements for security and usability.