خدمات آزمایشگاه شبکه‌های مبتنی بر IP

شما اینجا هستید

این آزمایشگاه، در خصوص محصولات و تجهیزات مرتبط با شبکه‌های VOIP، IP-PBX، NGN، هسته IMS و هسته LTE، قابلیت آزمون و تائید نمونه در قالب تطابق پروتکلها با استاندارد، کارکردی، سرویس و کارایی سیستم را دارد.

برخی از استانداردهای آزمون

  • RFC 2848: The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Service
  • RFC 2976: The SIP INFO Method
  • RFC 3050: Common Gateway Interface for SIP
  • RFC 3087: Control of Service Context using SIP Request-URI
  • RFC 3261: Official Main SIP RFC
  • RFC 3261: SIP: Session Initiation Protocol ‪(Main SIP RFC)‬
  • RFC 3262: Reliability of Provisional Responses in the Session Initiation Protocol ‪(SIP)‬
  • RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers
  • RFC 3264: An Offer/Answer Model with the Session Description Protocol ‪(SDP)‬
  • RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
  • RFC 3311: The Session Initiation Protocol (SIP) UPDATE Method
  • RFC 3312: Integration of Resource Management and Session Initiation Protocol ‪(SIP)‬
  • RFC 3313: Private Session Initiation Protocol (SIP) Extensions for Media Authorization
  • RFC 3319: Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers
  • RFC 3323: A Privacy Mechanism for the Session Initiation Protocol ‪(SIP)‬
  • RFC 3324: Short Term Requirements for Network Asserted Identity
  • RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
  • RFC 3326: The Reason Header Field for the Session Initiation Protocol ‪(SIP)‬
  • RFC 3327: Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
  • RFC 3329: Security Mechanism Agreement for the Session Initiation Protocol ‪(SIP)‬
  • RFC 3361: Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers
  • RFC 3388: Grouping of Media Lines in the Session Description Protocol ‪(SDP)‬
  • RFC 3420: Internet Media Type message
  • RFC 3428: Session Initiation Protocol (SIP) Extension for Instant Messaging
  • RFC 3485: The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression
  • RFC 3486: Compressing the Session Initiation Protocol ‪(SIP)‬
  • RFC 3487: Requirements for Resource Priority Mechanisms for the Session Initiation Protocol ‪(SIP)‬
  • RFC 3515: The Session Initiation Protocol (SIP) Refer Method
  • RFC 3524: Mapping of Media Streams to Resource Reservation Flows
  • RFC 3966: The tel URI for Telephone Numbers
  • RFC 4694: Number Portability Parameters for the ""‎tel"" URI
  • ITU-T Recommendation I.‎251.‎3, “Calling Line Identification Presentation (CLIP)”, Aug.‎ 1992.‎
  • ITU-T Recommendation I.‎252.‎4, “Call Forwarding Unconditional (CFU)”, Aug.‎ 1992.‎
  • ITU-T Recommendation I.‎252.‎2, “Call Forwarding Busy (CFB)”, Aug.‎ 1992.‎
  • ITU-T Recommendation I.‎252.‎3, “Call Forwarding No Reply (CFNR)”, Aug.‎ 1992.‎
  • ITU-T Recommendation I.‎253.‎1, “Call Waiting (CW)”, Jul.‎ 1990.‎
  • ITU-T Recommendation I.‎254.‎2, “Three-Party Supplementary Service”, Aug.‎ 1992.‎
  • ITU-T Recommendation I.‎254.‎1, “Multiparty supplementary services: Conference calling (CONF)”, Nov.‎ 1998.‎
  • RFC 1889, RTP: A Transport Protocol for Real-Time Applications, Obsoleted byRFC 3550.
  • RFC 3550, Standard 64,RTP: A Transport Protocol for Real-Time Applications
  • RFC 3551, Standard 65,RTP Profile for Audio and Video Conferences with Minimal Control
  • RFC 3190, RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio
  • RFC 6184, RTP Payload Format for H.‎264 Video
  • RFC 4103, RTP Payload Format for Text Conversation
  • RFC 3640, RTP Payload Format for Transport of MPEG-4 Elementary Streams
  • RFC 6416, RTP Payload Format for MPEG-4 Audio/Visual Streams
  • RFC 2250, RTP Payload Format for MPEG1/MPEG2 Video
  • RFC 4175, RTP Payload Format for Uncompressed Video
  • RFC 6295, RTP Payload Format for MIDI
  • RFC 4696, An Implementation Guide for RTP MIDI
  • RFC 7587, RTP Payload Format for the Opus Speech and Audio Codec
  • RFC 4961 Symmetric RTP ‎/ RTP Control Protocol ‪(RTCP)‬
  • RFC 3605 Real Time Control Protocol (RTCP) attribute in  Session Description Protocol (SDP

 

 

درباره ما

آزمایشگاه‌های مرجع تایید نمونه حوزه فناوری ارتباطات با هدف ارائه خدمات تایید نمونه و تخصصی و همچنین ایجاد بستر آزمون جهت انجام پروژه‌های کاربردی تاسیس گردیده‌اند.

ارتباط با ما

  • نشانی:    تهران، خیابان کارگرشمالی، روبروی سازمان انرژی اتمی، پژوهشگاه ارتباطات و فناوری ارتباطات
  • تلفن تماس: ۸۴۹۷۷۸۳۴
  • رایانامه: ctlabs@itrc.ac.ir