UCMA 3.0 - 无法呼叫或添加UCMA应用程序到会议 [英] UCMA 3.0 - Cannot call or add UCMA application to conference
本文介绍了UCMA 3.0 - 无法呼叫或添加UCMA应用程序到会议的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我们编写了一个应用程序，用于记录电话会议中与会者之间的Lync呼叫。我们创建了一个应用程序池和一个端点，并制作了证书。我们实施了会议录音，并以
测试目的直接拨打应用录音。 当我们直接调用录制应用程序时（来自Lync客户端），我们收到ID为304的错误（源ID 244）。使用Snooper查看我们在sip堆栈中有三个错误：
TL_INFO（TF_PROTOCOL）[0] 0B08.1B44： ：10/20 / 2011-13：53：41.648.000ff116（SIPStack，SIPAdminLog :: TraceProtocolRecord：SIPAdminLog.cpp（125））$$ begin_record
Trace-Correlation-Id：3960305916
Instance-Id ：000192B0
方向：收款
同行：recorder_machine.something.com:14500
消息类型：回复
起始价：SIP / 2.0 480暂时不可用
来自："Doe，John"< sip：johndoe@something.com> ;; tag = f0e1f22ded; epid = 09e8657b83
To：" RecordingDEV"< sip：recordingdev@something.com> ;; epid = 82EF4BFA85; tag = b8504ff385
CSeq：1 INVITE
Call-ID：c12966dede0546c4b57a525d6063ef2f
VIA：SIP / 2.0 / TLS xx.xx.xxx.161：60013; branch = z9hG4bK023DC616.F277571C82B61C95; branched = TRUE ，SIP / 2.0 / TLS xx.xx.xxx.9：21371; ms-received-port = 21371; ms-received-cid = 488D00
CONTENT-LENGTH：0
优先级：正常
支持：取代
P-ASSERTED-IDENTITY：" RecordingDEV"< SIP：recordingDEV@something.com>
警告：304 lcs.microsoft.com"媒体类型不可用"
Ms-Conversation-ID：AcyPL63Bv6345BOFRcWRO3YHdsO8UA ==
ms-diagnostics：24025; Component =" RTCC / 4.0.0.0_recording" ;; Reason =" No media handler for media type" ;; Source =" ; recorder_machine.something.com"
消息正文：–
$$ end_record
-------------------------- --------------------------------------------
TL_INFO（TF_PROTOCOL）[0] 0B08.1B44 :: 10/20 / 2011-13：53：41.650.0010002b（SIPStack，SIPAdminLog :: TraceProtocolRecord：SIPAdminLog.cpp（125） ）$$ begin_record
跟踪相关-Id：3960305916
实例-Id：000192B0
方向：传出
同行：xx.xx.xxx.9：21371
消息类型：响应
起始行：SIP / 2.0 480暂时不可用
来自："Doe，John"< sip：johndoe@something.com> ;; tag = f0e1f22ded; epid = 09e8657b83
收件人：" RecordingDEV"< sip：recordingdev@something.com> ;; epid = 82EF4BFA85; tag = b8504ff385
CSeq：1 INVITE
来电ID：c12966dede0546c4b57a525d6063ef2f
身份验证 - 信息：TLS-DSK qop =" auth"，opaque =" D664C5BA"，srand =" E0CE5D29"，snum =" 68"，rspauth =" 09d74aef4a0e5f9107396f24051d699a7a668cfe"，targetname =" lyncServer.something.com" ，realm =" SIP通信服务"，version = 4
Via：SIP / 2.0 / TLS xx.xx.xxx.9：21371; ms-received-port = 21371; ms-received-cid = 488D00
CONTENT-LENGTH ：0
优先级：正常
支持：替换
P-ASSERTED-IDENTITY："RecordingDEV"< sip：recordingDEV@something.com>
警告：304 lcs.microsoft.com"媒体类型不可用"
Ms-Conversation-ID：AcyPL63Bv6345BOFRcWRO3YHdsO8UA ==
ms-diagnostics：24025; Component =" RTCC / 4.0.0.0_recording" ;; Reason =" No media handler for media type" ;; Source =" ; recorder_machine.something.com"
消息正文：–
$$ end_record
---------------------- ------------------------------------------------
TL_INFO（TF_PROTOCOL）[0] 0B08.1B44 :: 10/20 / 2011-13：53：41.656.00100a58（SIPStack，SIPAdminLog :: TraceProtocolRecord：SIPAdminLog。 cpp（125））$$ begin_record
Trace-Correlation-Id：78562982
Instance-Id：000192B3
Direction：outgoing; source =" local"
同行：lyncServer.something.com:60146
消息类型：响应
起始行：SIP / 2.0 503服务不可用
来自：" RecordingDEV"< sip： recordingdev@something.com> ;; epid = 355094D4A8; tag = 9efb18a92
To：< sip：recordingdev@something.com:5061; transport = Tls; maddr = lyncServer.something.com> ;; tag = E3BE320E7DE40B884BACF47562242E16
CSeq：47 SERVICE
Call-ID：e810ba4bd40847f4a09ae49afd5b1b3c
Via：SIP / 2.0 / TLS xx.xx.xxx.161:60146; branch = z9hG4bK2d4983f0; ms-received-port = 60146; ms- received-cid = 489600
ms-diagnostics：2019; reason ="报告错误服务不可用" ;; source =" lyncServer.something.com"
服务器：RTC / 4.0
内容长度：0
消息正文：–
$$ end_record
但是如果尝试将应用程序插入在会议中，我们在Lync客户端上收到了另一个错误："此人正在使用不支持此类会议的程序"。 Snooper中的SIPStack看起来与上面类似。
在我们的应用程序启动期间，SIPStack出现错误：
TL_INFO（TF_PROTOCOL）[0] 0B08.111C :: 10/20 / 2011-14：13：08.759.001956b9 （SIPStack，SIPAdminLog :: TraceProtocolRecord：SIPAdminLog.cpp（125））$$ begin_record
Trace-Correlation-Id：973809947
Instance-Id：0001959F
Direction：outgoing; source ="本地"
Peer：recorder_machine.something.com:21419
消息类型：响应
起始行：SIP / 2.0 409冲突
来自：" RecordingDEV"< sip：recordingDEV @ something.com> ;; epid = 7C8B80C711; tag = c95ed63a59
To：< sip：recordingDEV@something.com> ;; epid = 7C8B80C711; tag = E3BE320E7DE40B884BACF47562242E16
CSeq：3 SERVICE
Call -ID：9b853a240f684579b784bf10701fb732
内容长度：1314
通过：SIP / 2.0 / TLS 10.65.106.9:21419; branch=z9hG4bK8e66da2;ms-received-port=21419;ms-ceceived-cid=48C400
ms-diagnostics：2044; reason =" Publication version out of date" ;; source =" lyncServer.something.com"
内容类型：application / msrtc-fault + xml
服务器：RTC / 4.0
消息正文：<故障>
< Faultcode> Client.BadCall.WrongDelta< / Faultcode>
< details>
< operation index =" 1"版本= QUOT; 0" curVersion = QUOT; 4英寸>
< state xmlns：xsi =" http：//www.w3.org/2001/XMLSchema-instance"的xmlns：XSD = QUOT; HTTP：//www.w3.org/2001/XMLSchema"的xmlns = QUOT; HTTP：//schemas.microsoft.com/2006/09/sip/state"的xsi：type = QUOT; aggregateState"><可用性及GT; 3500< /可用性和GT;< /状态>< /操作>
< operation index =" 2"版本= QUOT; 0" curVersion = QUOT; 4英寸>
< contactCard xmlns：xsi =" http：//www.w3.org/2001/XMLSchema-instance"的xmlns：XSD = QUOT; HTTP：//www.w3.org/2001/XMLSchema"的xmlns = QUOT; HTTP：//schemas.microsoft.com/2006/09/sip/contactcard"><同一性GT;<名称><显示名> RecordingDEV< /显示名>< /名称>< /同一性GT ;< automaton> true< / automaton>< type> automaton< / type>< delimiter xmlns =" http://schemas.microsoft.com/2006/09/sip/commontypes">< / delimiter> ;< / contactCard>< /操作>
< operation index =" 3"版本= QUOT; 0" curVersion = QUOT; 4英寸>
< services xmlns：xsi =" http：//www.w3.org/2001/XMLSchema-instance"的xmlns：XSD = QUOT; HTTP：//www.w3.org/2001/XMLSchema" xmlns =" http：//schemas.microsoft.com/2006/09/sip/service">< service uri =" sip：recordingDEV@something.com">< capabilities>< voice render = "真" capture =" true">< / voice>< text render =" false" capture =" false">< / text>< video render =" false"捕获= QUOT假QUOT;>< /视频>< /能力>< /服务>< /服务和GT;< /操作>
< / details>
< /故障>
$$ end_record
我不知道出了什么问题。任何人都可以帮助我吗？
解决方案
你能发布你正在使用的任何代码吗？在您的应用程序中接听电话？
此外，您的应用程序中的呼叫接收事件处理程序是否完全被调用，或者您是否在没有处理程序的情况下获得480响应？
We've written an application which would record Lync calls between participants in a conference call. We've created an application pool, and an endpoint, and made a certificate. We implemented both conference recording, and direct-call to app recording for testing purposes. When we call the recording application directly (from Lync client) we got an error with ID 304 (source ID 244). Looking with Snooper we got three errors in the sip stack:
TL_INFO(TF_PROTOCOL) [0]0B08.1B44::10/20/2011-13:53:41.648.000ff116 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record Trace-Correlation-Id: 3960305916 Instance-Id: 000192B0 Direction: incoming Peer: recorder_machine.something.com:14500 Message-Type: response Start-Line: SIP/2.0 480 Temporarily Unavailable From: "Doe, John"<sip:johndoe@something.com>;tag=f0e1f22ded;epid=09e8657b83 To: "RecordingDEV"<sip:recordingdev@something.com>;epid=82EF4BFA85;tag=b8504ff385 CSeq: 1 INVITE Call-ID: c12966dede0546c4b57a525d6063ef2f VIA: SIP/2.0/TLS xx.xx.xxx.161:60013;branch=z9hG4bK023DC616.F277571C82B61C95;branched=TRUE,SIP/2.0/TLS xx.xx.xxx.9:21371;ms-received-port=21371;ms-received-cid=488D00 CONTENT-LENGTH: 0 PRIORITY: Normal SUPPORTED: Replaces P-ASSERTED-IDENTITY: "RecordingDEV"<sip:recordingDEV@something.com> WARNING: 304 lcs.microsoft.com "Media type not available" Ms-Conversation-ID: AcyPL63Bv6345BOFRcWRO3YHdsO8UA== ms-diagnostics: 24025;Component="RTCC/4.0.0.0_recording";Reason="No application handler for media type";Source="recorder_machine.something.com" Message-Body: – $$end_record
----------------------------------------------------------------------
TL_INFO(TF_PROTOCOL) [0]0B08.1B44::10/20/2011-13:53:41.650.0010002b (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record Trace-Correlation-Id: 3960305916 Instance-Id: 000192B0 Direction: outgoing Peer: xx.xx.xxx.9:21371 Message-Type: response Start-Line: SIP/2.0 480 Temporarily Unavailable From: "Doe, John"<sip:johndoe@something.com>;tag=f0e1f22ded;epid=09e8657b83 To: "RecordingDEV"<sip:recordingdev@something.com>;epid=82EF4BFA85;tag=b8504ff385 CSeq: 1 INVITE Call-ID: c12966dede0546c4b57a525d6063ef2f Authentication-Info: TLS-DSK qop="auth", opaque="D664C5BA", srand="E0CE5D29", snum="68", rspauth="09d74aef4a0e5f9107396f24051d699a7a668cfe", targetname="lyncServer.something.com", realm="SIP Communications Service", version=4 Via: SIP/2.0/TLS xx.xx.xxx.9:21371;ms-received-port=21371;ms-received-cid=488D00 CONTENT-LENGTH: 0 PRIORITY: Normal SUPPORTED: Replaces P-ASSERTED-IDENTITY: "RecordingDEV"<sip:recordingDEV@something.com> WARNING: 304 lcs.microsoft.com "Media type not available" Ms-Conversation-ID: AcyPL63Bv6345BOFRcWRO3YHdsO8UA== ms-diagnostics: 24025;Component="RTCC/4.0.0.0_recording";Reason="No application handler for media type";Source="recorder_machine.something.com" Message-Body: – $$end_record
----------------------------------------------------------------------
TL_INFO(TF_PROTOCOL) [0]0B08.1B44::10/20/2011-13:53:41.656.00100a58 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record Trace-Correlation-Id: 78562982 Instance-Id: 000192B3 Direction: outgoing;source="local" Peer: lyncServer.something.com:60146 Message-Type: response Start-Line: SIP/2.0 503 Service unavailable From: "RecordingDEV"<sip:recordingdev@something.com>;epid=355094D4A8;tag=9efb18a92 To: <sip:recordingdev@something.com:5061;transport=Tls;maddr=lyncServer.something.com>;tag=E3BE320E7DE40B884BACF47562242E16 CSeq: 47 SERVICE Call-ID: e810ba4bd40847f4a09ae49afd5b1b3c Via: SIP/2.0/TLS xx.xx.xxx.161:60146;branch=z9hG4bK2d4983f0;ms-received-port=60146;ms-received-cid=489600 ms-diagnostics: 2019;reason="Report error service is not available";source="lyncServer.something.com" Server: RTC/4.0 Content-Length: 0 Message-Body: – $$end_record
However if try to insert the application into a conference we got another error on the Lync client: "This person is using a program that does not support this type of meeting". The SIPStack in Snooper looks similar to the above.
During the start of our application int the SIPStack there is an error:
TL_INFO(TF_PROTOCOL) [0]0B08.111C::10/20/2011-14:13:08.759.001956b9 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record Trace-Correlation-Id: 973809947 Instance-Id: 0001959F Direction: outgoing;source="local" Peer: recorder_machine.something.com:21419 Message-Type: response Start-Line: SIP/2.0 409 Conflict From: "RecordingDEV"<sip:recordingDEV@something.com>;epid=7C8B80C711;tag=c95ed63a59 To: <sip:recordingDEV@something.com>;epid=7C8B80C711;tag=E3BE320E7DE40B884BACF47562242E16 CSeq: 3 SERVICE Call-ID: 9b853a240f684579b784bf10701fb732 Content-Length: 1314 Via: SIP/2.0/TLS 10.65.106.9:21419;branch=z9hG4bK8e66da2;ms-received-port=21419;ms-received-cid=48C400 ms-diagnostics: 2044;reason="Publication version out of date";source="lyncServer.something.com" Content-Type: application/msrtc-fault+xml Server: RTC/4.0 Message-Body: <Fault> <Faultcode>Client.BadCall.WrongDelta</Faultcode> <details> <operation index="1" version="0" curVersion="4" > <state xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/2006/09/sip/state" xsi:type="aggregateState"><availability>3500</availability></state></operation> <operation index="2" version="0" curVersion="4" > <contactCard xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard"><identity><name><displayName>RecordingDEV</displayName></name></identity><automaton>true</automaton><type>automaton</type><delimiter xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes"></delimiter></contactCard></operation> <operation index="3" version="0" curVersion="4" > <services xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/2006/09/sip/service"><service uri="sip:recordingDEV@something.com"><capabilities><voice render="true" capture="true"></voice><text render="false" capture="false"></text><video render="false" capture="false"></video></capabilities></service></services></operation> </details> </Fault> $$end_record
I have no idea what is going wrong. Could anyone help me?
解决方案
Would you be able to post any of the code you are using to answer the call in your application?
Also, is the call received event handler in your application being invoked at all or are you getting the 480 response without the handler being hit at all?
这篇关于UCMA 3.0 - 无法呼叫或添加UCMA应用程序到会议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
