Fax error - what does this mean??

Discussion in '3CX Phone System - General' started by lonestar.computer, Apr 16, 2008.

Thread Status:
Not open for further replies.
  1. lonestar.computer

    Joined:
    Jan 27, 2008
    Messages:
    16
    Likes Received:
    0
    I am setting up a fax line to go to email. In the error server log we get "[MS010001] C:120.2:Answer provided. Connection(transcoding mode): media negotiation failed. No audio media specified."

    What does that mean? Thanks

    Here is the rest of the trace:

    12:17:06.515 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
    12:17:06.500 Call::Terminate [CM503008]: Call(112): Call is terminated
    12:17:06.500 Call::Terminate [CM503008]: Call(112): Call is terminated
    12:17:06.484 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
    12:17:06.484 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
    12:16:16.828 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:16.812 MediaServerReporting::RTPReceiver [MS105000] C:120.2: No RTP packets were received:remoteAddr=192.168.1.101:10010,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7128
    12:16:16.812 Call::Terminate [CM503008]: Call(120): Call is terminated
    12:16:16.812 Call::Terminate [CM503008]: Call(120): Call is terminated
    12:16:16.781 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:16.781 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:16.593 MediaServerReporting::SetRemoteParty [MS010001] C:120.2:Answer provided. Connection(transcoding mode): media negotiation failed. No audio media specified.
    12:16:16.593 CallLeg::setRemoteSdp Remote SDP is set for legC:120.2
    12:16:15.765 CallLeg::eek:nConfirmed Session 27260 of leg C:120.1 is confirmed
    12:16:15.656 CallCtrl::eek:nLegConnected [CM503007]: Call(120): Device joined: sip:888@192.168.1.101:5100;user=phone
    12:16:15.656 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:15.640 CallCtrl::eek:nLegConnected [CM503007]: Call(120): Device joined: sip:8179272044@psrveast.ga.broadvox.net:5060
    12:16:15.640 MediaServerReporting::SetRemoteParty [MS210003] C:120.1:Answer provided. Connection(transcoding mode):68.113.214.90:9012(9013)
    12:16:15.640 CallCtrl::eek:nAnsweredCall [CM503002]: Call(120): Alerting sip:888@192.168.1.101:5100;user=phone
    12:16:15.640 MediaServerReporting::SetRemoteParty [MS210001] C:120.2:Answer received. RTP connection: 192.168.1.101:10010(10011)
    12:16:15.640 CallLeg::setRemoteSdp Remote SDP is set for legC:120.2
    12:16:15.453 MediaServerReporting::SetRemoteParty [MS210002] C:120.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7128(7129)
    12:16:15.437 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(120): Calling: FaxBox:888@[Dev:sip:888@192.168.1.101:5100;user=phone]
    12:16:15.421 MediaServerReporting::SetRemoteParty [MS210000] C:120.1:Offer received. RTP connection: 64.158.162.71:8724(8725)
    12:16:15.421 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:106@192.168.1.101:5060;user=fax]
    12:16:15.421 CallLeg::setRemoteSdp Remote SDP is set for legC:120.1
    12:16:15.421 Line::printEndpointInfo [CM505003]: Provider:[BroadvoxFax] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.101:5060]
    12:16:15.421 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:15.328 CallCtrl::eek:nIncomingCall [CM503001]: Call(120): Incoming call from 8179231806@(Ln.10001@BroadvoxFax) to [sip:106@192.168.1.101:5060;user=fax]
    12:16:15.203 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10001 forwards to Fax:106
    12:16:15.031 CallLeg::eek:nNewCall [CM500002]: Info on incoming INVITE:
    INVITE sip:8179272044@192.168.1.101:5060 SIP/2.0
    Via: SIP/2.0/UDP 64.158.162.75:5060;branch=z9hG4bK0dB390c5c0b850d36b6
    Max-Forwards: 70
    Contact: [sip:8179231806@64.158.162.75:5060]
    To: [sip:8179272044@192.168.1.101]
    From: [sip:8179231806@64.158.162.75];tag=gK0d285d55
    Call-ID: 621641792_92595750@64.158.162.75
    CSeq: 5267 INVITE
    Session-Expires: 1800
    Min-SE: 90
    Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
    Allow: INVITE, ACK, CANCEL, BYE, REGISTER, REFER, INFO, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS
    Supported: timer
    P-Asserted-Identity: [sip:8179231806@64.158.162.75:5060]
    Content-Length: 0
     
  2. sunero

    Joined:
    Jul 7, 2008
    Messages:
    11
    Likes Received:
    0
    Did you get this problem solved, because I have the exact same problem?
     
  3. KrisHansen

    Joined:
    Apr 30, 2008
    Messages:
    22
    Likes Received:
    0
    Just overcame this, disable PBX delivers audio on the trunk which is delivering the Fax transmission.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. MatsW

    Joined:
    Mar 10, 2009
    Messages:
    50
    Likes Received:
    0
    I also have the same problem, but disabling "PBX delivers audio" didn't help. What could help thou is an explanation of what the log "media negotiation failed. No audio media specified" really means. Is this the fatal event that causes fax transmission to fail, or is it just an information message.
    Outgoing faxes work fine, but not incoming. I've also tried two different VoIP-providers with the same result (one of the was CellIP).
     
  5. KerryG

    KerryG Active Member

    Joined:
    Jun 19, 2009
    Messages:
    960
    Likes Received:
    0
    Faxing is one of the most difficult things for a PBX to deal with, and especially so if that fax is coming in over a SIP trunk. The moment you are trying to use VoIP to handle faxes, you fax reliability will drop significantly. Any latency or packet loss, even if you can't hear it on a regular voice call, will cause a FAX to fail. I HIGHLY recommend that you use regular POTS lines for faxing to ensure maximum reliability. Until everything is T.38, which I suspect is still 3-5 years out, faxing will continue to be an unreliable situation.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. MatsW

    Joined:
    Mar 10, 2009
    Messages:
    50
    Likes Received:
    0
    I've now incoming and outgoing got faxes to work by reducing the transmit and receive speed in my fax-server (Windows 2003) thru registry settings acc.to http://technet.microsoft.com/sv-se/library/cc780775(WS.10).aspx(HighestSendSpeed, ModemSendSpeeds and ModemRecieveSpeeds) and disabling T.38 in Grandstream FXS analog port gateway.
     
Thread Status:
Not open for further replies.