locked
500 Internal Server Error RRS feed

  • Question

  •  We are running

    OCS -- OCS Mediation Server -- Dialogic Media Gateway 300 -- BRI ISDN

    Client:             192.168.0.27        alimo-pc@domain.local
    OCS:               192.168.0.17        ocs.domain.local
    Mediation:      192.168.0.18         medi.domain.local
    Dialogic:         192.168.0.19

    Everything is configured and ready to go
    Outbound Calls go through all the way from the Communicator but rejects at the Dialogic end.
    While sniffing Packets at the Dialogic side all UDP SIP/RTP Packets are received at port: 0
    Which doesnt make sense as it should be received in media streaming range 60000/64000 which is configured from both ends Mediation and Dialogic.

    Below is the event log from the Communicator Client.

    Log Name:      Application
    Source:        Communicator
    Date:          1/12/2009 4:04:24 PM
    Event ID:      11
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      alimo-PC.domain.local
    Description:
    A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f4). More information is contained in the following technical data:
     
     RequestUri:   sip:+39993902@domain.local;user=phone
    From:         sip:alimo@domain.local;tag=b7eed62949
    To:           sip:+39993902@domain.local;user=phone;tag=6fe0a5731c
    Call-ID:      453a0f001e2c423c931ede3a97688f01
    Content-type: application/sdp;call-type=audiovideo

    v=0
    o=- 0 0 IN IP4 192.168.0.27
    s=session
    c=IN IP4 192.168.0.27
    b=CT:53980
    t=0 0
    m=audio 13824 RTP/AVP 114 111 112 115 116 4 8 0 97 101
    k=base64:zW76qrGoIR8mKq0+z5n/FrTadwHzJSP0qmXLSN58evrN/CyDsBNza6QhUqU7
    a=candidate:3n6/1maldbh1xndh3kh48G3+UKWKiC3GA/mu9WSvPrE 1 yUBnJ75n0T7BKzC+1ah81g UDP 0.900 192.168.0.27 13824
    a=candidate:3n6/1maldbh1xndh3kh48G3+UKWKiC3GA/mu9WSvPrE 2 yUBnJ75n0T7BKzC+1ah81g UDP 0.900 192.168.0.27 27392
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:ci6ZEWV9/qQzYJXLCDniUdZ+SA9Hqv3+cTQ24snn|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:0c0bdXVHUkHNlpNtX02FVeyvMQvHUvs0tMK/j1Df|2^31|1:1
    a=maxptime:200
    a=rtcp:27392
    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:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:optional


    Response Data:

    101  Progress Report
    ms-diagnostics:  12006;reason="Trying next hop";source="ocs.domain.local";PhoneUsage="CN={C491D082-9CD3-4A41-9A79-9DCEE38670EB},CN=Phone Route Usages,CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local";PhoneRoute="Universal Route";Gateway="medi.domain.local:5061";appName="OutboundRouting"


    183  Session Progress


    500  Internal Server Error
    Ms-diagnostics:  0;source="medi.domain.local";reason="Internal error";component="MediationServer";Exception="Unable to establish a connection.";GatewayFqdn="192.168.0.19"

     
     Resolution:
     If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

    Monday, January 12, 2009 1:41 PM

Answers

  •  It was the windows firewall on Dialogic side and it worked perfectly and all calls went through just by adding an exception to the port 5060 in the windows firewall.
    • Marked as answer by alimoh Wednesday, January 14, 2009 8:18 AM
    Wednesday, January 14, 2009 8:18 AM