Media Gateway Control Protocol (MGCP) Return Code Usage

Foster, Bill; Sivachelvan, C.

doi:10.17487/rfc3661

Cited by 3 publications

(1 citation statement)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“… Use VLANs to separate the voice traffic from the data traffic.  Disable the unused signaling protocols such as IAX2 [35], [36] (Inter-Asterisk eXchange 2), H.323 [37], MGCP [38] (Media Gateway Control Protocol), and Cisco SCCP (Skinny Call Control Protocol).  Encrypt the traffic of the trunk between the Elastix server and the ITSP.…”

Section: O Good Practices and Recommendationsmentioning

confidence: 99%

A Set of Policies and Guidelines for Deploying Safer VoIP Solutions

Araneo¹,

Gamess²,

Urribarri³

2018

IJCTE

View full text Add to dashboard Cite

Attacks on networks which implement VoIP could lead to the degradation of the IP PBX performance, the interception of conversations, the theft of important and confidential information, and the generation of large expenses in any organization, if they do not have the correct security mechanisms. VoIP is based on existing layers and protocols and therefore inherits their security issues. In relation to signalization, different protocols have been proposed for VoIP. However, the Session Initiation Protocol (SIP) tends to be the favorite one because it is standardized by the IETF and has many features. Similarly to any other Internet protocol, SIP is susceptible to security threads, and can be involved in different kinds of attacks. In this paper, we propose three basic scenarios, representing common fundamental network architectures for VoIP, from which more complex systems can be built. We also establish a set of policies and guidelines focused on the aforementioned architectures, in order to mitigate security threads and provide more effective solutions for existing vulnerabilities in VoIP.

show abstract

Section: O Good Practices and Recommendationsmentioning

confidence: 99%