1 / 15

v4/v6 dual stack voip network planning case study : TANET VOIP 交換平台

v4/v6 dual stack voip network planning case study : TANET VOIP 交換平台. 顯赫資訊 Kaiser. 教育部自編門號 超過千所學校互連 封閉型編碼 標準 sip 協定. 教育部交換平台. 9xx-yyyyy 9xx, 單位 (14 區網， 25 縣市網） V4 only now. Voip numbering. IP v4/v6 in UA (IP-Phone, GW, softphone…. ) Proxy server IP-PBX (B2BUA)

inga
Download Presentation

v4/v6 dual stack voip network planning case study : TANET VOIP 交換平台

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. v4/v6 dual stack voip network planningcase study : TANET VOIP 交換平台 顯赫資訊 Kaiser www.gentrice.net

  2. 教育部自編門號 超過千所學校互連 封閉型編碼 標準sip協定 教育部交換平台 www.gentrice.net

  3. 9xx-yyyyy 9xx, 單位 (14區網，25縣市網） V4 only now Voip numbering www.gentrice.net

  4. IP v4/v6 in UA (IP-Phone, GW, softphone…. ) Proxy server IP-PBX (B2BUA) Application (ex: MCU, enum…) We can not replace all IPv4 SIP device over night UA (CPE) support dual stack SIP server support dual stack Heavy loading in sip for sip translation between 4/6. IP v4/v6 issue in voip service www.gentrice.net

  5. CPE Dual stack? Dual UA ? Server V6 in a single thread V4 voip is stable now V4 + V6 dual transport B2BUA Translation RTP header rewrite No P2P GW None in market VoIP IPv6 www.gentrice.net

  6. Call type V4<-->V4 V4<-->V6 V6<-->V6 Translation Signaling , need to be done in B2BUA RTP V6 logo Enum SIP server www.gentrice.net

  7. Test items www.gentrice.net

  8. Application layer SIP is plain text Broken V4 UA Host:port 192.168.0.100:5060 v6 addr fe80::219:e3ff:fe05:42a0 SIP Message www.gentrice.net

  9. IPv4 Nat issue IPv6 V6 to V6, no problem (expect B2BUA) V4 to V6 V6 to V4 Peer to Peer VoIP www.gentrice.net

  10. 有效降低 v4/v6 上的voip轉換 話機需能支援302後的new invite Server需能判斷話機是否支援dual stack 302 move temporary www.gentrice.net

  11. 302 call flow PROXY(dual stack) 45670(dual stack) 45674(IPv4 only) 1.INVITE(IPv6) 2.302 Move Temporarily (IPv6) 3.200 OK(IPv6) 4.INVITE(IPv4) 5.INVITE(IPv4) 6.200 OK(IPv4) 7.200 OK(IPv4) 8.ACK(IPv4) 9.ACK(IPv4) RTP Stream(IPv4) Source:台南市教育局 www.gentrice.net

  12. www.gentrice.net

  13. Case study • 雲林縣 • All ip-phone in v6 network, now over 1000+ phone • PSTN GW still in v4 • 桃園、澎湖 follow v6 only in ipphone • 台南 • V6 in new phone number block • V6 call first, v4 failfall • 北縣 • V4 major, V6 in selected phone www.gentrice.net

  14. V6 IP-Phone • Too many v4 only NAT box in campus • IP-PHONE 跑v6造成困難 • Core switch/ L2/ L3 switch • TANET release more v4 IP to reduce NAT environment. www.gentrice.net

  15. 結論 • V6 可有效加速voip deployment • 日本企業網路優先配發v6 • dual stack 是未來趨勢 • 如果降低v4/v6轉換是未來service provider需考量的一環 • 新的相關參數的制定 • 台灣經驗 www.gentrice.net

More Related