MOC sends IP Address of A/V Edge on SDP RRS feed

  • Question

  • Hello,
    I'm setting up a PBX integration with OCS. OCS - PBX calls are working fine, however PBX - OCS are not. Looking on the UCCP logs on the MOC client, I see that it's sending on SDP, the IP address of the A/V Edge Server, instead of the IP address of the client PC itself. Due to this, media path is never established.
    Did anybody seem this before?


    Luciano Mello
    Thursday, June 11, 2009 12:08 AM

All replies

  • Hello Luciano,

    Did you also install a mediation server and added this server to your routes in your voice properties?



    Microsoft Unified Communications (Dutch) Blog @ www.MsUC.nl
    • Proposed as answer by R Stevens Thursday, June 11, 2009 6:39 AM
    Thursday, June 11, 2009 6:38 AM
  • ____ Stevens

    Sorry for not being clear. Yes, Mediation Server is in place, activated, with certificate correctly installed and such. Also, MG is a Dialogic DMG2000, which is Microsoft qualified for this type of integration. Also, Voice Properties (Location Profile, Phone Usages, Policies and Routes) are set properly.
    This is the 200 OK sent from the MOC PC:

    06/10/2009|18:27:29.028 13A4:1008 INFO  :: Sending Packet - (From Local Address: 2689 bytes:
    06/10/2009|18:27:29.028 13A4:1008 INFO  :: SIP/2.0 200 OK
    Via: SIP/2.0/TLS;branch=z9hG4bK06B8AB42.CF1DAF35;branched=TRUE;ms-internal-info="cb_i3BymkaV1HqSiWoVUh62J99vPrPHa81XuZosgAA"
    Via: SIP/2.0/TLS;branch=z9hG4bK12bab394;ms-received-port=4848;ms-received-cid=B300
    From: <sip:+51122667@grupoib.local;user=phone>;epid=1E8682A82A;tag=304626a0ff
    To: "" <sip:+51127101@grupoib.local;user=phone>;epid=3111f4207f;tag=5caada6201
    Call-ID: d1913d5d-db9c-4f11-be9f-1c41608faa54
    CSeq: 1 INVITE
    Record-Route: <sip:ocs.grupoib.local:5061;transport=tls;ms-fe=s31rp1.grupoib.local;ms-role-rs-from;lr;ms-identity=ILHY3xPMw7kWzMO5aaIqJJ5bt2inAksI66pMXjUff2-xXPHa81trGppAAA;ms-route-sig=aafqLnOCtPbatMVbzsVOTeH58AserPHa81trGppAAA>;tag=9C1E7A570341216764E2BA9F15E644BF
    Contact: <sip:testocs1@intercorp.com.pe;opaque=user:epid:UIAiuflfVVu4XGw3KCll8QAA;gruu>
    User-Agent: UCCP/2.0.6362.129 OC/2.0.6362.129 (Microsoft Office Communicator)
    Supported: Replaces
    P-Preferred-Identity: <sip:testocs1@intercorp.com.pe>, <tel:+51127101>
    Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="16CCA1CB", targetname="sip/s31rp1.grupoib.local", crand="a3231eac", cnum="12", response="602306092a864886f71201020201011100ffffffff9d82c9953ba6cdf2f209ae78f9a4fe0e"
    Content-Type: application/sdp
    Content-Length: 1370

    o=- 0 0 IN IP4
    c=IN IP4
    t=0 0
    m=audio 51174 RTP/SAVP 111 115 8 0 97 101
    a=candidate:rN5fUulO6fC/Zyz2s8nMFcxLbHq8fvMYjPLhOIEuQWE 1 P3ccXtgQ1stTcadA9imK/A UDP 0.830 11401
    a=candidate:rN5fUulO6fC/Zyz2s8nMFcxLbHq8fvMYjPLhOIEuQWE 2 P3ccXtgQ1stTcadA9imK/A UDP 0.830 19069 a=candidate:sit1KRhfxzfnZmekDC1vPp+6MJVLWHwdZrRQhjOnCKs 1 Q/oRB85ZFb2p20OGqIOpVQ TCP 0.190 54694 a=candidate:sit1KRhfxzfnZmekDC1vPp+6MJVLWHwdZrRQhjOnCKs 2 Q/oRB85ZFb2p20OGqIOpVQ TCP 0.190 54694 a=candidate:bqSHLBGGYH/CL+hPG2G02cSZTFOJrb4uXHpsgv/g3YA 1 JBh25EAwddND8B0w+4nInQ UDP 0.490 51174
    a=candidate:bqSHLBGGYH/CL+hPG2G02cSZTFOJrb4uXHpsgv/g3YA 2 JBh25EAwddND8B0w+4nInQ UDP 0.490 56598 a=candidate:iwcnENCLXPj/Y0bgGrXwXBDKq/o09RArmGy63iwCFfg 1 zYMvx6Q8ITW6TQswQLbUNg TCP 0.250 1250 a=candidate:iwcnENCLXPj/Y0bgGrXwXBDKq/o09RArmGy63iwCFfg 2 zYMvx6Q8ITW6TQswQLbUNg TCP 0.250 1250
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:cBt7EmTdc24Av1jWxftxEF6Tnv72+YXiDtNwlIlR|2^31|1:1
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16

    What is confusing me is that the MOC PC address ( appears as candidate, but the actual IP sent on  media parameter ( is the A/V Edge External address.
    Any hints on why this is happening? Have in mind that the MOC PC is on the internal network, on the same net as the FE/Mediation/etc (don't be mislead by the IPs - 130.x.x.x is internal and 192.168.x.x is public, on this scenario).


    Luciano Mello

    Thursday, June 11, 2009 12:41 PM
  • Hello all,

    Sadly, I ended up on the "I got it fixed... Just don't know what happened" situation. I was on the try-and-error process, when I decided to remove all references to Edge Server on the Front-End. After doing that and restarting the services, the problem remained, so I put it all back and restarted again.
    After sometime, I tried the call again and it's now working. Hopefully it won't show up again Unfortunately, I don't have more time to dive into this, so I'm moving on, but I still welcome any hints, even guesses to what might happened.
    And yes, I triple-checked the configuration to make sure I re-entered exactly what was there before removing.

    Thanks to all,


    Thursday, June 11, 2009 9:23 PM