3cx / Quintum Tenor AX

Discussion in '3CX Phone System - General' started by Haavok, Apr 9, 2010.

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

    Joined:
    Apr 9, 2010
    Messages:
    3
    Likes Received:
    0
    Hello,

    I have a 3cx server configured to use a Quintum Tenor AX which is connected to the PSTN. Below are 2 calls.

    The bottom (below the "=") is a call inbound from the PSTN. That call gets connected to the 3cx server and forwarded to a softphone extension that I have setup. The call gets answered but not hearing any audio. I'm assuming it's probably a codec issue or the fact that the inbound call is from a cell phone.

    The call between the "#" and "=" is the one that's really puzzling me. When I call the phone # from the softphone, the trunk never shows an outbound connection and the call just keeps ringing and ringing but never actually hits the PSTN.

    Is there anything that someone might be able to suggest as to the reason why outbound from the 3cx server isn't connecting to the PSTN? I'm planning on posting this same question to a Quintum forum.

    Kindly use code and /code tags when posting server logs
    Code:
    19:10:24.995  [MS105000] C:10.1: No RTP packets were received:remoteAddr=192.168.1.199:10286,extAddr=0.0.0.0:0,localAddr=192.168.1.81:7036
    19:10:23.088  [CM503008]: Call(11): Call is terminated
    19:10:12.370  [CM503025]: Call(11): Calling PSTNline:12135551212@(Ln.10000@MSH-Quintum-PSTN)@[Dev:sip:10000@192.168.1.199:5060]
    19:10:12.370  [MS210002] C:11.2:Offer provided. Connection(transcoding mode): 192.168.1.81:7044(7045)
    19:10:12.323  [CM503004]: Call(11): Route 1: PSTNline:12135551212@(Ln.10000@MSH-Quintum-PSTN)@[Dev:sip:10000@192.168.1.199:5060,Dev:sip:10001@192.168.1.199:5061,Dev:sip:10002@192.168.1.199:5062,Dev:sip:10003@192.168.1.199:5063,Dev:sip:10004@192.168.1.199:5064,Dev:sip:10005@192.168.1.199:5065,Dev:sip:10006@192.168.1.199:5066,Dev:sip:10007@192.168.1.199:5067,Dev:sip:10008@192.168.1.199:5068,Dev:sip:10009@192.168.1.199:5069,Dev:sip:10010@192.168.1.199:5070,Dev:sip:10011@192.168.1.199:5071,Dev:sip:10012@192.168.1.199:5072,Dev:sip:10013@192.168.1.199:5073,Dev:sip:10014@192.168.1.199:5074,Dev:sip:10015@192.168.1.199:5075,Dev:sip:10016@192.168.1.199:5076,Dev:sip:10017@192.168.1.199:5077,Dev:sip:10018@192.168.1.199:5078,Dev:sip:10019@192.168.1.199:5079,Dev:sip:10020@192.168.1.199:5080,Dev:sip:10021@192.168.1.199:5081,Dev:sip:10022@192.168.1.199:5082,Dev:sip:10023@192.168.1.199:5083]
    19:10:12.323  [MS210000] C:11.1:Offer received. RTP connection: 127.0.0.1:10028(10029)
    19:10:12.323  [CM503010]: Making route(s) to <sip:12135551212@192.168.1.102:5060>
    19:10:12.307  Remote SDP is set for legC:11.1
    19:10:12.307  [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] PBX contact: [sip:101@127.0.0.1:5060]
    19:10:12.307  [CM503001]: Call(11): Incoming call from Ext.101 to <sip:12135551212@192.168.1.102:5060>
    19:10:12.307  [CM500002]: Info on incoming INVITE:
      INVITE sip:12135551212@192.168.1.102:5060 SIP/2.0
      Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-d8754z-b92b534f9b352a4d-2---d8754z-;rport=5080;received=192.168.1.102
      Via: SIP/2.0/UDP 10.0.1.109:2869;branch=z9hG4bK-d8754z-tunneltid-1---d8754z-;rport
      Via: SIP/2.0/UDP 127.0.0.1:2868;branch=z9hG4bK-d8754z-b92b534f9b352a4d-1---d8754z-;rport=2868
      Max-Forwards: 68
      Record-Route: <sip:3cxBridge@127.0.0.1:5080;user=proxy;uri="10.0.1.109:2869">
      Contact: <sip:101@127.0.0.1:2868;rinstance=c678e9fafb9aa80e>
      To: <sip:12135551212@192.168.1.102:5060>
      From: "Jim"<sip:101@192.168.1.102:5060>;tag=9842985d
      Call-ID: YjY1OWQzMmUwYTVhZTJmNjQ3ZDk3YWM0YjhiOTgxZTc.
      CSeq: 2 INVITE
      Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
      Proxy-Authorization: Digest username="101",realm="3CXPhoneSystem",nonce="414d535c01cdcc0394:c3ec508c792c7a55e1a83adc0be2dedf",uri="sip:12135551212@192.168.1.102:5060",response="edef2b24af73352676d85625813355d6",algorithm=MD5
      Supported: replaces
      User-Agent: 3CXPhone 4.0.10858.0
      Content-Length: 0

    ===========================================================



    Code:
    19:10:09.073  Active calls counted toward license limit: []
    19:09:51.729  [CM503008]: Call(10): Call is terminated
    19:09:45.291  Session 135534 of leg C:10.1 is confirmed
    19:09:45.166  [CM503007]: Call(10): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=4121230b89e78cb3
    19:09:45.166  [CM503007]: Call(10): Device joined: sip:10000@192.168.1.199:5060
    19:09:45.166  [MS210003] C:10.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.1.81:7036(7037)
    19:09:45.166  [MS210001] C:10.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40622(40623)
    19:09:45.166  Remote SDP is set for legC:10.3
    19:09:45.166  [CM503002]: Call(10): Alerting sip:EndCall@127.0.0.1:40600;rinstance=4121230b89e78cb3
    19:09:44.948  [CM503025]: Call(10): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=4121230b89e78cb3]
    19:09:44.948  [MS210002] C:10.3:Offer provided. Connection(transcoding mode): 127.0.0.1:7040(7041)
    19:09:44.948  [CM503016]: Call(10): Attempt to reach <sip:101@192.168.1.102:5060> failed. Reason: Busy
    19:09:44.948  [CM503003]: Call(10): Call to sip:101@192.168.1.102:5060 has failed; Cause: 486 Busy Here; from IP:127.0.0.1:5080
    19:09:40.620  [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] PBX contact: [sip:101@127.0.0.1:5060]
    19:09:40.620  [CM503002]: Call(10): Alerting sip:101@127.0.0.1:2868;rinstance=c678e9fafb9aa80e
    19:09:40.135  [CM503025]: Call(10): Calling Ext:Ext.101@[Dev:sip:101@127.0.0.1:2868;rinstance=c678e9fafb9aa80e]
    19:09:40.135  [MS210002] C:10.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7038(7039)
    19:09:40.104  [CM503004]: Call(10): Route 1: Ext:Ext.101@[Dev:sip:101@127.0.0.1:2868;rinstance=c678e9fafb9aa80e]
    19:09:40.088  [MS210000] C:10.1:Offer received. RTP connection: 192.168.1.199:10286(10287)
    19:09:40.088  [CM503010]: Making route(s) to <sip:101@192.168.1.102:5060>
    19:09:40.088  Remote SDP is set for legC:10.1
    19:09:40.088  [CM505002]: Gateway:[MSH-Quintum-PSTN] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Quintum/1.0.0 SN/0030E1403179 SW/P107-09-00] PBX contact: [sip:10000@192.168.1.81:5060]
    19:09:40.088  [CM503001]: Call(10): Incoming call from 10000@(Ln.10000@MSH-Quintum-PSTN) to <sip:101@192.168.1.102:5060>
    19:09:40.073  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:101
    19:09:40.073  Looking for inbound target: called=10000; caller=10000
    19:09:40.073  [CM500002]: Info on incoming INVITE:
      INVITE sip:10000@192.168.1.102 SIP/2.0
      Via: SIP/2.0/UDP 192.168.1.199;branch=z9hG4bK-tenor-401b-19c7-62562
      Max-Forwards: 70
      Contact: <sip:10000@192.168.1.199>
      To: <sip:10000@192.168.1.102>
      From: <sip:10000@192.168.1.102>;tag=401b19c7-680
      Call-ID: call-714A8413-A124-2D10-1C01-5E@192.168.1.199
      CSeq: 2 INVITE
      Expires: 180
      Proxy-Authorization: Digest realm="3CXPhoneSystem",nonce="414d535c01cdcbe378:2aea017800d700eab0a5f475a30a429d",algorithm=MD5,username="10000",uri="sip:10000@192.168.1.102",response="2c7ee04f6d198c3574a8aab37a060cc9"
      Supported: 100rel
      User-Agent: Quintum/1.0.0 SN/0030E1403179 SW/P107-09-00
      Content-Length: 0
      Session-GUID: 878862947-1667314531-858783744-140
      Quintum: 0c01030b033130360714000000000000000c006c09808080803130303030080531303030301301000f0b413035322d343033313739
     
  2. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Try to call it from locally installed soft- or hardphone. I mean not behind a bridge.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Haavok

    Joined:
    Apr 9, 2010
    Messages:
    3
    Likes Received:
    0
    I've tried to call it from a softphone on the same system that the 3cx server is installed on.... same results. It doesn't connect to the trunk to go out the PSTN.

    (Sorry for not quoting the log snippet properly)
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,889
    Likes Received:
    190
    I would suggest using a 3Cx supported gateway. The Quintum is not supported.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Haavok

    Joined:
    Apr 9, 2010
    Messages:
    3
    Likes Received:
    0
    Of course you do and I understand your reasoning behind that but I'm doing this for a remote client who doesn't have the $$ for another gateway.

    I ran Wireshark and found that the 3cx server is sending the SIP address out of the server and over to the gateway so I'm going to assume 3cx is doing it's job and it's the Quintum that's having issues. I can post a capture of the traffic but based on this thread... help will be extremely limited because of the Quintum not being supported.

    Thanks anyway.
     
Thread Status:
Not open for further replies.