文档章节

例子:H.323到SIP的呼叫

帝都老白
 帝都老白
发布于 2015/03/03 11:05
字数 926
阅读 25
收藏 0
H.323 to SIP Call

In this example, a H.323 terminal calls a SIP-enabled PC through a H.323/SIP gateway. The gateway does signaling translation between the protocols but allows the two end points to exchange media packets directly with each other. The full details of SIP/H.323 interworking are being developed in the SIP working group [4].

In this example, shown in Figure , the initial message exchange is between the calling H.323 terminal and the H.323 gatekeeper. The gatekeeper resolves the H.323 alias into an address served by the H.323/SIP gateway. The ACF response indicates that gatekeeper-routed signaling is required, so the Q.931 and H.245 TCP connections are opened to the gatekeeper, which opens TCP connections to the gateway. The calling H.323 terminal sends a Q.931 Setup message to the gatekeeper, which proxies it to the H.323/SIP gateway. The gateway then looks up the H.323 alias and resolves it to the SIP URI of the called party. It constructs an INVITE from the Setup message and forwards it to a SIP proxy, which forwards it to the called party. Note that because the Setup message does not contain any media information, the INVITE does not contain any media information either. The called party sends a 180 Ringing then a 200 OK to indicate that the call has been answered. The media information present in the SDP message body is stored by the gateway, which sends Alerting and Connect messages.

 
Figure 10.6: H.323 to SIP call.

Messages are sent to the gatekeeper, which proxies them to the calling H.323 terminal. The gateway holds off sending the ACK response to the INVITE until the H.245 media exchange is completed between the H.323 terminal and the gateway. Once that is complete, the negotiated media capabilities are returned in the ACK and the media session begins.

M1   ARQ
     address(h323alias=Stibitz)


M2   ACF
     gatekeeper routed signaling


M3   Setup
     Cd address(h323alias=Stibitz)
     Cg address(h323alias=Burroughs)


M4   Setup
     Cd address(h323alias=Stibitz)
     Cg address(h323alias=Burroughs)


M5   ARQ


M6   ACF


M7   INVITE sip:stibitz@proxy.com SIP/2.0
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544    TCP used for transport
     Max-Forwards: 70
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE                              CSeq initialized to 43252
     Contact: <sip:burroughs@h323-gateway.com;transport=tcp>
     Content-Length: 0
M8   100 Trying
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     From: <sip:burroughs@h323-gateway.com>
     To: <sip:stibitz@proxy.com>
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Content-Length: 0


M9   INVITE sip:gstibitz123@snailmail.com SIP/2.0
     Via: SIP/2.0/TCP 3.4.5.6:5060;branch=z9hG4bK452.1
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     Max-Forwards: 69
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Contact: <sip:burroughs@h323-gateway.com;transport=tcp>


M10  SIP/2.0 180 Ringing
     Via: SIP/2.0/TCP 3.4.5.6:5060; branch=z9hG4bK452.1
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Contact: <sip:gstibitz123@snailmail.com;transport=tcp>
     Content-Length: 0


M11  SIP/2.0 180 Ringing
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     From: <sip:burroughs@h323-gateway.com>
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Contact: <sip:gstibitz123@snailmail.com;transport=tcp>
     Content-Length: 0


M12  Alerting


M13  Alerting


M14  SIP/2.0 200 OK
     Via: SIP/2.0/TCP 3.4.5.6:5060; branch=z9hG4bK452.1
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Contact: <sip:gstibitz123@snailmail.com;transport=tcp>
     Content-Type: application/sdp
     Content-Length: 134

     v=0
     o=George 2890844576 2890844576 IN IP4 4.30.19.04
     s=-
     t=0 0
     c=IN IP4 4.30.19.04
     m=audio 5004 RTP/AVP 0
     a=rtpmap:0 PCMU/8000


M15  SIP/2.0 200 OK
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK544
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 INVITE
     Contact: <sip:gstibitz123@snailmail.com>
     Content-Type: application/sdp
     Content-Length: 134

     v=0
     o=George 2890844576 2890844576 IN IP4 4.30.19.04
     s=-
     t=0 0
     c=IN IP4 4.30.19.04
     m=audio 5004 RTP/AVP 0
     a=rtpmap:0 PCMU/8000


M16  Connect


M17  Connect


M18  TerminalCapabilitySet


M19  TerminalCapabilitySet


M20  TerminalCapabilitySetAck


M21  TerminalCapabilitySetAck


M22  TerminalCapabilitySet


M23  TerminalCapabilitySet


M24  TerminalCapabilitySetAck


M25  TerminalCapabilitySetAck


M26  MasterSlaveDetermination


M27  MasterSlaveDetermination


M28  MasterSlaveDeterminationAck


M29  MasterSlaveDeterminationAck


M30  OpenLogicalChannel
     g711uLaw 1.28.18.57 60002


M31  OpenLogicalChannel
     g711uLaw 1.28.18.57 60002


M32  OpenLogicalChannelAck


M33  OpenLogicalChannelAck
     Call Flow Examples 181


M34  OpenLogicalChannel
     g711uLaw 4.30.19.04 5004


M35  OpenLogicalChannel
     g711uLaw 4.30.19.04 5004


M36  OpenLogicalChannelAck


M37  OpenLogicalChannelAck


M38  ACK sip:gstibitz123@snailmail.com SIP/2.0
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK32
     Max-Forwards: 70
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 ACK
     Content-Type: application/sdp
     Content-Length: 130

     v=0
     o=- 2890844577 2890844577 IN IP4 1.28.18.57
     s=-
     t=0 0
     c=IN IP4 1.28.18.57
     m=audio 60002 RTP/AVP 0
     a=rtpmap:0 PCMU/8000


M39  ACK sip:gstibitz123@snailmail.com SIP/2.0
     Via: SIP/2.0/TCP 3.4.5.6:5060;branch=z9hG4bK452.1
     Via: SIP/2.0/TCP 2.3.4.5:4344;branch=z9hG4bK532
     Max-Forwards: 69
     From: <sip:burroughs@h323-gateway.com>;tag=3q526g45
     To: <sip:stibitz@proxy.com>;tag=1926
     Call-ID: 526272332146783569054
     CSeq: 43252 ACK
     Content-Type: application/sdp
     Content-Length: 130

     v=0
     o=- 2890844577 2890844577 IN IP4 1.28.18.57
     s=-
     t=0 0
     c=IN IP4 1.28.18.57
     m=audio 60002 RTP/AVP 0
     a=rtpmap:0 PCMU/8000

本文转载自:http://blog.csdn.net/ioke/article/details/150193

上一篇: MacApp
帝都老白
粉丝 15
博文 54
码字总数 150719
作品 0
朝阳
CTO(技术副总裁)
私信 提问
开源多点会议单元--OpenMCU

OpenMCU-ru 是一个使用H.323,SIP 和 RTSP 协议的开源多点会议单元(软件MCU)。 从原始的OpenMCU衍生出来。服务器运行在Linux,Windows和FreeBSD上。 特征: 通过端口1420的Web界面的配置和...

匿名
2016/06/30
1K
0
Ekiga 4.0.0 发布,视频会议系统

Ekiga 4.0.0 版本对主窗口进行了重大的改变,重新增加了 H264 和 H263+ 视频插件,新的 pulse 音频插件,新的音频编码器:SILK (used by skype), G.722.1 (aka Siren 7), and G.722.2 (aka G...

oschina
2012/11/27
5.3K
4
软交换协议比较和发展趋势 (SIP-T和SIP-I的比较)

BICC是直接面向电话业务的应用提出的,来自传统的电信阵营,具有更加严谨的体系架构,因此它能为在软交换中实施现有电路交换电话网络中的业务提供很好的透明性。相比之下,SIP的体系架构则不...

AlphaJay
2010/09/24
0
1
电话引擎--Yate

Yate (Yet Another Telephony Engine ) 是下一代的电话引擎,使用 VoIP 和 PSTN 协议。 Yate 可作为: VoIP server VoIP client Conference server - with up to 200 channels in a singl......

匿名
2010/03/08
15.8K
1
Yate 5.2 发布,电话引擎

Yate 5.2 更好的支持 JavaScript,修复了内存泄漏问题,支持 YateBTS 2.0. Yate (Yet Another Telephony Engine ) 是下一代的电话引擎,使用 VoIP 和 PSTN 协议。 Yate 可作为: VoIP ser...

oschina
2014/03/18
3.5K
1

没有更多内容

加载失败,请刷新页面

加载更多

掌握生成对抗网络(GANs),召唤专属二次元老婆(老公)不是梦

全文共6706字,预计学习时长12分钟或更长 近日,《狮子王》热映,其逼真的外形,几乎可以以假乱真,让观众不禁大呼:awsl,这也太真实了吧! 实体模型、CGI动画、实景拍摄、VR等技术娴熟运用...

读芯术
27分钟前
1
0
C#经典面试题100道

1. .NET和C#有什么区别 答:.NET一般指 .NET FrameWork框架,它是一种平台,一种技术。 C#是一种编程语言,可以基于.NET平台的应用。 2.一列数的规则如下: 1、1、2、3、5、8、13、21、34......

元歌
30分钟前
0
0
重磅!容器集群监控利器 阿里云Prometheus 正式免费公测

Prometheus 作为容器生态下集群监控的首选方案,是一套开源的系统监控报警框架。它启发于 Google 的 borgmon 监控系统,并于 2015 年正式发布。2016 年,Prometheus 正式加入 Cloud Native C...

阿里云云栖社区
31分钟前
1
0
LeetCode 160: 相交链表 Intersection of Two Linked Lists

爱写Bug(ID:iCodeBugs) 编写一个程序,找到两个单链表相交的起始节点。 Write a program to find the node at which the intersection of two singly linked lists begins. 如下面的两个链...

iCodeBugs
33分钟前
2
0
hadoop yarn漏洞 8088端口进入挖矿病毒处理记录

早上发现服务器cpu使用异常 进程如图所示 按照挖矿病毒的套路 肯定是定时任务不停地执行脚本 遂查看定时任务 进入/var/spool/cron 查看定时任务 发现里面有一个root文件 定时任务每分钟执行一...

詹姆斯-高斯林
37分钟前
0
0

没有更多内容

加载失败,请刷新页面

加载更多

返回顶部
顶部