Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

dead air when using fax server

Discussion in '3CX Phone System - General' started by tlachau, Feb 16, 2016.

Thread Status:
Not open for further replies.
  1. tlachau

    Joined:
    Dec 3, 2015
    Messages:
    13
    Likes Received:
    0
    Hi,

    I'm new to 3CX and we've just setup our server. I am trying to get the fax to email to work and have not been getting it to work.
    What we are seeing is the fax extension is not ringing and picking up. When I dial the DID attached to the fax extension it is just dead air. I assume I should hear the fax tone...

    We are running 3cx 14. I've setup a Fax extension under the Fax section as extension 8888. It is setup to inbound route the DID 6419876543 to "send fax to email extension 8888" .

    What am I missing?

    Here is some information from the activity logs

    16-Feb-2016 10:24:14.651 NAT/ALG check:L:953.1[Line:10000<<17151234567] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:14.523 NAT/ALG check:L:953.2[Fax] REQUEST 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:12.950 NAT/ALG check:L:953.1[Line:10000<<17151234567] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:12.819 NAT/ALG check:L:953.2[Fax] REQUEST 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:11.307 NAT/ALG check:L:953.1[Line:10000<<17151234567] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:11.004 NAT/ALG check:L:953.2[Fax] REQUEST 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:09.516 [CM503007]: Call(C:953): Fax:8888 has joined, contact <sip:8888@127.0.0.1:5006>
    16-Feb-2016 10:24:09.512 [CM503007]: Call(C:953): Line:10000<<17151234567 has joined, contact <sip:6419876543@10.91.15.8:5060>
    16-Feb-2016 10:24:09.510 L:953.2[Fax] has joined to L:953.1[Line:10000<<17151234567]
    16-Feb-2016 10:24:09.510 NAT/ALG check:L:953.2[Fax] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:09.453 [CM503025]: Call(C:953): Calling T:Fax:8888@[Dev:sip:8888@127.0.0.1:5006;user=phone] for L:953.1[Line:10000<<17151234567]
    16-Feb-2016 10:24:09.412 [CM503027]: Call(C:953): From: Line:10000<<17151234567 ("+17151234567" <sip:17151234567@nwphone.federalfoam.com:5060>) to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5006;user=phone]
    16-Feb-2016 10:24:09.412 [CM503004]: Call(C:953): Route 1: from L:953.1[Line:10000<<17151234567] to T:Fax:8888@[Dev:sip:8888@127.0.0.1:5006;user=phone]
    16-Feb-2016 10:24:09.412 [CM505003]: Provider:[Sangoma-SBC] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [NetBorder Session Controller] PBX contact: [sip:6419876543@10.91.15.10:5060]
    16-Feb-2016 10:24:09.410 [CM503001]: Call(C:953): Incoming call from Line:10000<<17151234567 to <sip:8888@10.91.15.10:5060>
    16-Feb-2016 10:24:09.410 Line limit check: Current # of calls for line Lc:10000(@Sangoma-SBC[<sip:6419876543@10.91.15.8:5060>]) is 1; limit is 15
    16-Feb-2016 10:24:09.410 NAT/ALG check:L:953.1[Line:10000<<17151234567] REQUEST 'INVITE' - basic check passed. No information for extended checks
    16-Feb-2016 10:24:09.406 [MS006000] C:953.1: connection address is enforced to 10.91.15.10
    16-Feb-2016 10:24:09.399 [CM503012]: Inbound any hours rule (flowroute main 2231) for 10000 forwards to Fax:8888
    16-Feb-2016 10:23:44.678 Leg L:952.2[Line:10000>>17635775789] is terminated: Cause: BYE from PBX
    16-Feb-2016 10:23:44.677 [CM503008]: Call(C:952): Call is terminated
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,079
    Likes Received:
    324
  3. tlachau

    Joined:
    Dec 3, 2015
    Messages:
    13
    Likes Received:
    0
    Yes incoming provider supports t38. Call trace shows that the call is staying as g711 instead of t38.

    We are using a sangoma sbc to register to the provider and pass traffic to the 3cx server.

    Any idea if this is maybe on the sangoma side, and if so any experience with making sure that t38 is enabled on that device. I'm not seeing it anywhere in any of the menus...
     
  4. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,375
    Likes Received:
    84
Thread Status:
Not open for further replies.