locked
Internal MOC users cannot start a voice conversations with external MOC users RRS feed

  • Question

  •  

    Hello all,

     

    Since I finished install my microsoft office communications edge server, External users can start voice conversations with other external users. Although Internal users can start voice conversations with other internal users but, there is no way to start voice conversations between external and internal.

     

    I'm using one edge server with two nics (one in the DMZ, one in the LAN)

     

     

    Please advise,

    Assaf

    Sunday, March 9, 2008 3:49 PM

Answers

  • Ok,

    I've found the solution, I added a public IP to the A/V Edge server and it solved the issue.

     

    thanks for everything

    Assaf

     

    Thursday, March 13, 2008 8:19 AM

All replies

  • Are you sure that you have configured a public routable IP Address for your AV EDGE Server?

    Check the EDGE deployment guide for details

     

    http://www.microsoft.com/downloads/details.aspx?familyid=ED45B74E-00C4-40D2-ABEE-216CE50F5AD2&displaylang=en

     

    Johan

     

    Sunday, March 9, 2008 11:17 PM
  • Do not understand,

    I configured a public IP that's how external users can connect to my edge server.

    is there any other public ip that I should configure?

     

    thanks,

    Assaf

     

    Monday, March 10, 2008 7:38 AM
  •  

    Hi.

     

    A/V Edge server must have public routable IP because STUN server.

    If there no public IP on A/V Edge server then Audio and Video with external users doesn't work.

     

    Best regards.

    Maciek

    Monday, March 10, 2008 9:01 AM
  • The A/V conferences work just between two external users, but with one external and one internal it doesn't work.

     

    Monday, March 10, 2008 9:04 AM
  • Hi.

     

    Can You check event log and Sip Stack on Edge and OCS ? What can You see when connection error appear.

     

    Best regards.

    Maciek

     

    Monday, March 10, 2008 9:15 AM
  • There are no events at all, the only thing I can find is when I try to validate my A/V conferencing server I get the following error:

     

    A/V Authentication Edge Server: Could not contact A/V Authentication Edge Server.
    To resolve this error, check for the following
    1. The outbound proxy is reachable.
    2. The outbound proxy and A/V Authentication Edge Server are in trusted server list of each other.
    3. The outbound proxy and A/V Authentication Edge Server have valid certificates.
    4. Conference Server certificate is valid.
    5. A/V Authentication Edge Server Gruu is correct.

     

    I tested and find that the A/V  server can Reach A/V Authentication Edge Server using port 5062, also there are no problems with the certificate.

     

     

    thanks,

    Assaf

     

     

     

    Monday, March 10, 2008 10:12 AM
  • Hi.

     

    Can You check forest Global properties ? There is Edge Servers Tab. Check it if the configuration is set to properly fqdn and port (5062) .

     

    Best regards.

    Maciek

    Monday, March 10, 2008 10:44 AM
  • It's configured that way.

     

    Assaf,

     

    Monday, March 10, 2008 10:51 AM
  • Hi.

     

    Can You run Loging tool to gather sip stack data on Edge and OCS ?

    Please provide results as attachment.

     

    BTW. Have You tried to restart services on Edge and OCS ?

     

    Best regrads.

    Maciek

     

     

     

    Monday, March 10, 2008 11:58 AM
  • the relevant errors that I can find attached:

     

    Edge server:

     

    SIP-Start-Line: SIP/2.0 503 Service unavailable
    SIP-Call-ID: 548341e32b5b4c1e8a0a0c809d811ec3
    SIP-CSeq: 1 SERVICE
    Peer: 80.179.11.70:3251
    Data: destination="test.comm@tescom-intl.com"
    $$end_record
    TL_INFO(TF_PROTOCOL) [0]127C.09F4::03/10/2008-12:53:54.089.000047fd (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
    Instance-Id: 0000003F
    Direction: outgoing;source="internal edge";destination="external edge"
    Peer: 80.179.11.70:3251
    Message-Type: response
    Start-Line: SIP/2.0 503 Service unavailable
    From: "test comm"<sip:test.comm@tescom-intl.com>;tag=bb8aa0ebe8;epid=ce5c77781a
    To: <sip:test.comm@tescom-intl.com>;tag=AB0D49409239072C4D572B1A6C4A45D4
    CSeq: 1 SERVICE
    Call-ID: 548341e32b5b4c1e8a0a0c809d811ec3
    ms-user-logon-data: RemoteUser
    Authentication-Info: NTLM rspauth="01000000000000006D58A3E9C2A0DF12", srand="2F794957", snum="20", opaque="BC47EDDB", qop="auth", targetname="tm1ocs.TESCOM.NET", realm="SIP Communications Service"
    Content-Length: 74
    Via: SIP/2.0/TLS 192.168.255.12:3251;received=80.179.11.70;ms-received-port=3251;ms-received-cid=300
    ms-diagnostics: 2019;reason="Report error service is not available";source="tm1ocs.TESCOM.NET"
    Retry-After: 90
    Content-Type: application/msrtc-fault+xml
    Message-Body: <Fault>
    <Faultcode>Server.Unavailable.ReportError</Faultcode>
    </Fault>
    $$end_record

    Front End Server:

    SIP-Start-Line: SIP/2.0 503 Service unavailable
    SIP-Call-ID: 548341e32b5b4c1e8a0a0c809d811ec3
    SIP-CSeq: 1 SERVICE
    Peer: tm1ocs.TESCOM.NET:2826
    Data: destination="tm1ocs.TESCOM.NET"
    $$end_record
    TL_INFO(TF_PROTOCOL) [0]1648.1670::03/10/2008-12:53:54.147.00003121 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
    Instance-Id: 000043AE
    Direction: outgoing;source="local"
    Peer: tm1ocs.TESCOM.NET:2826
    Message-Type: response
    Start-Line: SIP/2.0 503 Service unavailable
    From: "test comm"<sip:test.comm@tescom-intl.com>;tag=bb8aa0ebe8;epid=ce5c77781a
    To: <sip:test.comm@tescom-intl.com>;tag=AB0D49409239072C4D572B1A6C4A45D4
    CSeq: 1 SERVICE
    Call-ID: 548341e32b5b4c1e8a0a0c809d811ec3
    Authentication-Info: NTLM rspauth="01000000000000006D58A3E9C2A0DF12", srand="2F794957", snum="20", opaque="BC47EDDB", qop="auth", targetname="tm1ocs.TESCOM.NET", realm="SIP Communications Service"
    Content-Length: 74
    Via: SIP/2.0/TLS 10.10.50.229:2826;branch=z9hG4bK0A6BC7BF.78A4828B;branched=FALSE;ms-received-port=2826;ms-received-cid=1A800
    Via: SIP/2.0/TLS 192.168.255.12:3251;received=80.179.11.70;ms-received-port=3251;ms-received-cid=300
    ms-diagnostics: 2019;reason="Report error service is not available";source="tm1ocs.TESCOM.NET"
    Retry-After: 90
    Content-Type: application/msrtc-fault+xml
    Message-Body: <Fault>
    <Faultcode>Server.Unavailable.ReportError</Faultcode>
    </Fault>
    $$end_record

     

    thanks,

    Assaf

    Monday, March 10, 2008 1:04 PM
  • Hi all,

     

    Please help me with this issue,

    I'm really stuck in the integration.

     

     

    thanks,

     

    Tuesday, March 11, 2008 9:26 AM
  • Did you run the validation wizard on your EDGE server?

    Verify that there are no errors.

     

    Edge Server Deployment Guide

    http://www.microsoft.com/downloads/details.aspx?FamilyId=ED45B74E-00C4-40D2-ABEE-216CE50F5AD2&displaylang=en

     

    Johan

     

    Tuesday, March 11, 2008 9:30 PM
  • Hi Johan,

     

    I ran the validation wizard on the EDGE server, and it succeded succesfully.

     

    When I run the validation on the A/V front end server I have a connection error with the A/V authentication.

    I tried to run a sniffer on the Edge server and I find out that all connections from internal Front End server doesn't accept by the edge server.

     

     

    thanks,

    Assaf

     

    Wednesday, March 12, 2008 6:31 AM
  • Ok,

    I've found the solution, I added a public IP to the A/V Edge server and it solved the issue.

     

    thanks for everything

    Assaf

     

    Thursday, March 13, 2008 8:19 AM
  • I did ask you to check for a Public IP in my first response on this thread

    This could have been resolved much faster!

     

    Johan

    Thursday, March 13, 2008 8:43 AM