z-logo
open-access-imgOpen Access
Client‐based Internet Protocol version 4‐Internet Protocol version 6 translation mechanism for Session Initiation Protocol multimedia services in next generation networks
Author(s) -
Chen WhaiEn,
Li SsuHsien
Publication year - 2013
Publication title -
iet networks
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.466
H-Index - 21
ISSN - 2047-4962
DOI - 10.1049/iet-net.2012.0084
Subject(s) - session initiation protocol , computer science , ipv4 , sip trunking , computer network , ipv6 , internet protocol , internet protocol control protocol , next generation network , testbed , user datagram protocol , voice over ip , rtp control protocol , internet protocol suite , the internet , network packet , operating system , server
In the ‘Next Generation Networks’, ‘Session Initiation Protocol’ (SIP) is widely used to control multimedia (e.g. voice and video) sessions and ‘Internet Protocol version 6’ (IPv6) is adopted to provide enough addressing space. However, in the current stage of IPv6 deployment, the newly IPv6‐enabled device [i.e. typically internet protocol version 4 (IPv4)/IPv6 dual‐stack device] may connect to an existing IPv4 device. In the traditional ‘server‐based solutions’, the SIP server is modified to perform the IPv4–IPv6 translations to the SIP messages and the real‐time transport protocol (RTP) packets. However, the IPv4–IPv6 translations increase the call setup latency, the RTP transmission delay and the packet loss possibility. To reduce the drawbacks, this study proposes a ‘client‐based solution’, where the client (i.e. the end device) instead of the SIP server performs the IPv4–IPv6 translation. The authors utilise the message flows to elaborate three server based and the proposed client‐based solutions. In addition, the authors implement all solutions and deploy them in an IPv4–IPv6 interworking testbed. By using the testbed, the authors analyse these solutions in terms of the ‘UA modification, the SIP Server modification, the call setup complexity and the RTP translation’.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here