locked
in the OCS 2007 and R2 Mediation Server, why the signaling sent by the mediation server is different, the FROM tag is changed,line uri does not work. RRS feed

  • Question

  • in the OCS 2007 and R2 Mediation Server, why the signaling sent by the mediation server is different, the FROM tag is changed.
    I build two  OCS test Servers,one is based on OCS 2007, the other is based on OCS 2007 R2, I have a Media Gateway connected to mediation server.
    I config the oc user lltt,line uri is tel:+12345678. make a call from oc r2(the test client is oc r2).
    I get the signaling  log from the Media Gateway, I find the two version mediation server send different singnaling, The FROM tag is different. see below.

    I want to know where I can config the R2 server to make the behavior as same as the ocs 2007 server ?


    -----------OCS2007 send------------------------------
    [02/06 12:06:36.748521]SIP: recv from IP[192.168.4.241:4046], id=0, len=[896],msg=
    INVITE sip:10000@192.168.4.249;user=phone SIP/2.0
    FROM: <sip:+12345678@medi.ocsTest.com;user=phone>;epid=33DA796582;tag=805989cc2c
    TO: <sip:10000@192.168.4.249;user=phone>
    CSEQ: 1 INVITE
    CALL-ID: 044668c6-560e-4b19-98f2-f40cda6ddf0c
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TCP 192.168.4.241:4046;branch=z9hG4bK66ff984
    CONTACT: <sip:medi.ocsTest.com:5060;transport=Tcp;maddr=192.168.4.241;ms-opaque=5c09e5d6f677d964>
    CONTENT-LENGTH: 305
    SUPPORTED: 100rel
    USER-AGENT: RTCC/3.0.0.0 MediationServer
    CONTENT-TYPE: application/sdp; charset=utf-8
    ALLOW: UPDATE
    ALLOW: Ack, Cancel, Bye,Invite



    -----------OCS 2007 R2 send---------------------------------------
    [02/06 11:53:51.389828]SIP: recv from IP[192.168.4.240:3124], id=0, len=[894],msg=
    INVITE sip:1000@192.168.4.249;user=phone SIP/2.0
    FROM: <sip:lltt@r2so.com>;epid=E99D75FB7F;tag=3267f10d4
    TO: <sip:1000@192.168.4.249;user=phone>
    CSEQ: 1 INVITE
    CALL-ID: 49895774-ded3-491e-ae9e-17f5014d0b54
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TCP 192.168.4.240:3124;branch=z9hG4bK3c4e97b1
    CONTACT: <sip:MediaR2.R2So.com:5060;transport=Tcp;maddr=192.168.4.240;ms-opaque=c7c7d31022bc0c1b>
    CONTENT-LENGTH: 329
    SUPPORTED: 100rel
    USER-AGENT: RTCC/3.5.0.0 MediationServer
    CONTENT-TYPE: application/sdp; charset=utf-8
    ALLOW: UPDATE
    ALLOW: Ack, Cancel, Bye,Invite








    Baal
    Saturday, February 6, 2010 4:54 AM

All replies

  • I use OCS log tool,catch the log from mediation server. I notice that there are difference , --> Local URI: sip:+12345678@medi.ocsTest.com & Local URI: sip:lltt@r2so.com
    -------------ocs 2007 mediation log ---------------------
    TL_INFO(TF_PROTOCOL) [0]0508.0B54::02/06/2010-05:38:32.811.0000000a (MediationServer,MediationCall.CreateOutgoingSession:746.idx(663))( 0273E403 )$$START-MEDIATIONSERVER
    MediationCall: 750a29936c8c4150b48c33be8d904be8
    CallId: 7d9e9f2dfa9d4184a85b8ea3cfc220d6
    From: sip:lltt@ocstest.com
    To: sip:10000@medi.ocsTest.com:5061;user=phone;maddr=medi.ocsTest.com
    Direction: Outbound
    Start-Line: Creating outgoing Session. Local URI: sip:+12345678@medi.ocsTest.com;user=phone, Remote Uri: sip:10000@192.168.4.249;user=phone $$END-MEDIATIONSERVER


    -----------ocs 2007 R2 mediation log ---------------------
    TL_INFO(TF_PROTOCOL) [0]0394.026C::02/06/2010-05:55:24.060.00000004 (MediationServer,MediationCall.CreateOutgoingSession:mediationcall.cs(1028))( 00000000023C0C5D )$$START-MEDIATIONSERVER
    MediationCall: 3c3cb80d8ba244a4b71d147a408c8ec3
    CallId: d3718ed882ae4341a07fedf8f13aa0db
     From: sip:lltt@r2so.com
    To: sip:1000@MediaR2.R2So.com:5061;user=phone;maddr=MediaR2.R2So.com
    Direction: Outbound
    Start-Line: Creating outgoing Session. Local URI: sip:lltt@r2so.com, Remote Uri: sip:1000@192.168.4.249;user=phone $$END-MEDIATIONSERVER
    Baal
    Saturday, February 6, 2010 6:11 AM
  • maybe need a hotfix?


    Baal
    Saturday, February 6, 2010 7:05 AM
  • Never saw that behaviour; I always get tel URI in FROM in OCS R2 environment.

    Johann
    Johann Deutinger | MCTS Exchange 2007 / OCS 2007
    Sunday, February 7, 2010 9:16 PM
  • I think it's a OCS R2 bug.
    Baal
    Monday, February 8, 2010 1:57 AM