locked
Call terminated on media connectivity failure - OCS R2 AV Edge RRS feed

  • Question

  • I have an ocs R2 edge server behind an ISA 2006 Sp1 everything is configured as required this is my second deployment which mirrors this one the other deployment is working fine. All calls from an internal client to internal or intternal to external fucntion properly, however I cannot make any phone calls from a Remote User connected communicator client, I cannot make any internal or external calls when the calls tries to connect I recieve this message in the snooper trace:

    Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity failure"

    I've gone all over all the settings and compared to my previous deployment and everything is configured the same. I've verified the timezone's are correct on all servers, can someone please provide some insight to resolve this issue.

    Regards
    Habib

    Monday, August 24, 2009 3:01 AM

Answers

  • Ok here is what i've done, I finally got the AV server to be able to make calls via ISA 2006 Sp1, I had some remanants of ip information on the nics which i thought were cleared but were not.

    However the video will not work. The only way around it , is to set the AV edge ip address to be a public IP address I used the windows firewall on that nic card to open the appropriate ports and the video portion began to work and works within the live meeting as well.

    Thanks to everyone for the insight and randy for looking at the logs for me.

    Habib

    Thursday, September 3, 2009 3:41 PM

All replies

  • If you use ISA Server as your firewall, configuring it as a NAT is not supported because ISA Server 2006 does not support static NAT.

    More info
    http://technet.microsoft.com/en-gb/library/dd441361(office.13).aspx
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Monday, August 24, 2009 2:31 PM
  • I only have 1 ISA server between the internet and my OCS R2 edge setup in a 3 Leg Perimeter network and I have configured my ISA server as per the link you specified, however I am still having this issue.
    Monday, August 24, 2009 2:59 PM
  • Have you seen this article?

    Securing OCS with ISA Server
    http://technet.microsoft.com/en-us/magazine/2009.03.isa.aspx?pr=blog

    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Monday, August 24, 2009 3:02 PM
  • Habib,

    Can you specify whether you are attempting to use NAT or have a public IP addresses assigned directly to the A/V Edge interface?
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, August 24, 2009 3:49 PM
    Moderator
  • Jeff;

    I have a public IP directly assigned to the AV edge interface and I can ping the address from a remote location. As previously meantioned I have another deployement setup in the same manner and can make phone calls internally, externally, AV works in a live meeting session. But it is not working here.

    Habib
    Monday, August 24, 2009 7:09 PM
  • Can you verify you can telnet to your A/V edge on port 443 from the External client?

    Also can you enable logging in the communicator client of the external client, zip it and email it to me at rwintle@winxnet.com I could take a peak. I did a lot of troubleshooting lately with a similar issue, it was related ot the external clients not publishing the proper candidate list because it could not initiate an https connection with the A/V Edge.


    Randy Wintle | MCTS: UC Voice Specialization | WinXnet Inc
    Thursday, August 27, 2009 2:16 PM
  • Randy;

    I've sent you over the logs.

    Thanks
    Habib
    Thursday, August 27, 2009 2:30 PM
  • I can see from the first look that the external client is not advertising all of its candidate information, when I had this issue however we could not connect to the AV Edge on port 443.

    ------=_NextPart_000_0003_01CA25CD.E1DFBBA0

    Content-Type: application/sdp

    Content-Transfer-Encoding: 7bit

    Content-Disposition: session; handling=optional; ms-proxy-2007fallback

    v=0

    o=- 0 0 IN IP4 192.168.1.4

    s=session

    c=IN IP4 192.168.1.4

    b=CT:99980

    t=0 0

    m=audio 12695 RTP/AVP 114 111 112 115 116 4 8 0 97 13 118 101

    k=base64:SUTXLCF2KMzYrR12xOEs3uM5IFrP9b0NoWcGJEl6ybhLu3rQ1DRHQt/jLDSy

    a=candidate:mM5Jwm20lnvcH8DNBBM0vGTxR4PdxFeixnfgtbRrQ3s 1 xd7XqMiCyNKz5LFtZIc2kA UDP 0.830 192.168.1.4 12695

    a=candidate:mM5Jwm20lnvcH8DNBBM0vGTxR4PdxFeixnfgtbRrQ3s 2 xd7XqMiCyNKz5LFtZIc2kA UDP 0.830 192.168.1.4 15809

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:dRHFo0z3LVMdEtiWhxd6pwh1VjGb9HIdWKUoBaDl|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:97CLpJ+Eo29haBLqACtKXgMOgoVQakOdVaziH+29|2^31|1:1

    a=maxptime:200

    a=rtcp:15809

    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    a=rtpmap:111 SIREN/16000

    a=fmtp:111 bitrate=16000

    a=rtpmap:112 G7221/16000

    a=fmtp:112 bitrate=24000

    a=rtpmap:115 x-msrta/8000

    a=fmtp:115 bitrate=11800

    a=rtpmap:116 AAL2-G726-32/8000

    a=rtpmap:4 G723/8000

    a=rtpmap:8 PCMA/8000

    a=rtpmap:0 PCMU/8000

    a=rtpmap:97 RED/8000

    a=rtpmap:13 CN/8000

    a=rtpmap:118 CN/16000

    a=rtpmap:101 telephone-event/8000

    a=fmtp:101 0-16

    a=encryption:optional

    ------=_NextPart_000_0003_01CA25CD.E1DFBBA0

    Content-Type: application/sdp

    Content-Transfer-Encoding: 7bit

    Content-Disposition: session; handling=optional

    v=0

    o=- 0 0 IN IP4 192.168.1.4

    s=session

    c=IN IP4 192.168.1.4

    b=CT:99980

    t=0 0

    m=audio 22101 RTP/AVP 114 111 112 115 116 4 8 0 97 13 118 101

    k=base64:SUTXLCF2KMzYrR12xOEs3uM5IFrP9b0NoWcGJEl6ybhLu3rQ1DRHQt/jLDSy

    a=ice-ufrag:vwDl

    a=ice-pwd:Dhq/F3oN7idwI83NXCzbVfqO

    a=candidate:1 1 UDP 2130706431 192.168.1.4 22101 typ host

    a=candidate:1 2 UDP 2130705918 192.168.1.4 14655 typ host

    a=candidate:3 1 TCP-ACT 1684798719 192.168.1.4 22101 typ srflx raddr 192.168.1.4 rport 22101

    a=candidate:3 2 TCP-ACT 1684798206 192.168.1.4 22101 typ srflx raddr 192.168.1.4 rport 22101

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:dRHFo0z3LVMdEtiWhxd6pwh1VjGb9HIdWKUoBaDl|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:97CLpJ+Eo29haBLqACtKXgMOgoVQakOdVaziH+29|2^31|1:1

    a=maxptime:200

    a=rtcp:14655

    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    a=rtpmap:111 SIREN/16000

    a=fmtp:111 bitrate=16000

    a=rtpmap:112 G7221/16000

    a=fmtp:112 bitrate=24000

    a=rtpmap:115 x-msrta/8000

    a=fmtp:115 bitrate=11800

    a=rtpmap:116 AAL2-G726-32/8000

    a=rtpmap:4 G723/8000

    a=rtpmap:8 PCMA/8000

    a=rtpmap:0 PCMU/8000

    a=rtpmap:97 RED/8000

    a=rtpmap:13 CN/8000

    a=rtpmap:118 CN/16000

    a=rtpmap:101 telephone-event/8000

    a=fmtp:101 0-16

    a=encryption:optional

    Exactly why this is notw orking i'm not entirely sure yet, i'll review all logs more and get back to you.


    Randy Wintle | MCTS: UC Voice Specialization | WinXnet Inc
    Thursday, August 27, 2009 5:50 PM
  • Ok here is what i've done, I finally got the AV server to be able to make calls via ISA 2006 Sp1, I had some remanants of ip information on the nics which i thought were cleared but were not.

    However the video will not work. The only way around it , is to set the AV edge ip address to be a public IP address I used the windows firewall on that nic card to open the appropriate ports and the video portion began to work and works within the live meeting as well.

    Thanks to everyone for the insight and randy for looking at the logs for me.

    Habib

    Thursday, September 3, 2009 3:41 PM