Can not catch incomming calls !

Discussion in '3CX Phone System - General' started by Ahmadi, Sep 17, 2009.

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

    Joined:
    Sep 17, 2009
    Messages:
    10
    Likes Received:
    0
    Hi
    First,In my first post i must say,Thank you for 3CX Phone System, Its great software.
    Im configured my intalled 3CX Phone System fully but 3CX don't accept incomming calls.
    NOTE: I readed some topics about "Unidentified incoming call. Review INVITE and adjust source identification" and i did all of the toipcs solutions but no one worked for me! I mean that I have inbound rule, DID, and other things
    Here is some of the topics that i did them:
    http://www.3cx.com/forums/incoming-sip-call-not-working-6974.html#p49203
    http://www.3cx.com/forums/can-t-receive-incoming-calls-11231.html#p57424

    Im using one PSDN device(one E1) and no voip provider!
    Here is my log:
    Code:
    20:08:44.145  [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    
      INVITE sip:2@10.45.20.17:5060 SIP/2.0
    
      Via: SIP/2.0/UDP 10.45.20.20:5060;branch=z9hG4bK371A3
    
      Max-Forwards: 70
    
      Contact: <sip:2243111@10.45.20.20:5060>
    
      To: <sip:2@10.45.20.17>
    
      From: <sip:2243111@10.45.20.20>;tag=F2B7C74-1991
    
      Call-ID: 37DD9CCE-177011D5-81E2D663-60D0DBC3@10.45.20.20
    
      CSeq: 101 INVITE
    
      Expires: 180
    
      Min-SE: 1800
    
      Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
    
      Date: Wed, 14 Mar 2001 05:18:01 GMT
    
      Supported: 100rel, timer, resource-priority, replaces
    
      Timestamp: 984547081
    
      User-Agent: Cisco-SIPGateway/IOS-12.x
    
      Allow-Events: telephone-event
    
      Content-Length: 0
    
      Remote-Party-ID: <sip:2243111@10.45.20.20>;party=calling;screen=yes;privacy=off
    
      Cisco-Guid: 937230502-393220565-2151481378-2438463526
    
      
    
    
    20:08:44.144  [CM302001]: Authorization system can not identify source of: SipReq:  INVITE 2@10.45.20.17:5060 tid=371A3 cseq=INVITE contact=2243111@10.45.20.20:5060 / 101 from(wire)
    
    20:08:37.920  [CM503008]: Call(4): Call is terminated
    
    20:08:34.904  [CM503002]: Call(4): Alerting sip:10000@10.45.20.20:5060
    
    20:08:34.774  [CM503024]: Call(4): Calling Unknown:2243111@(Ln.10000@gateway1)@[Dev:sip:10000@10.45.20.20:5060]
    
    20:08:34.766  [CM503004]: Call(4): Route 1: Unknown:2243111@(Ln.10000@gateway1)@[Dev:sip:10000@10.45.20.20:5060]
    
    20:08:34.756  [CM503010]: Making route(s) to "2243111"<sip:2243111@10.45.20.17>
    
    20:08:34.751  [CM505001]: Ext.100: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1103k stamp 53621] Transport: [sip:10.45.20.17:5060]
    
    20:08:34.744  [CM503001]: Call(4): Incoming call from Ext.100 to "2243111"<sip:2243111@10.45.20.17>
    
    20:08:18.176  [CM503008]: Call(3): Call is terminated
    
    20:08:13.665  [CM503002]: Call(3): Alerting sip:10000@10.45.20.20:5060
    
    20:08:13.533  [CM503024]: Call(3): Calling Unknown:2243111@(Ln.10000@gateway1)@[Dev:sip:10000@10.45.20.20:5060]
    
    20:08:13.526  [CM503004]: Call(3): Route 1: Unknown:2243111@(Ln.10000@gateway1)@[Dev:sip:10000@10.45.20.20:5060]
    
    20:08:13.515  [CM503010]: Making route(s) to "2243111"<sip:2243111@10.45.20.17>
    
    20:08:13.512  [CM505001]: Ext.100: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1103k stamp 53621] Transport: [sip:10.45.20.17:5060]
    
    20:08:13.504  [CM503001]: Call(3): Incoming call from Ext.100 to "2243111"<sip:2243111@10.45.20.17>
    
     
  2. discovery1

    discovery1 Member

    Joined:
    Aug 4, 2008
    Messages:
    355
    Likes Received:
    0
    Code:
    20:08:44.145  [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    
      INVITE sip:2@[b]10.45.20.17[/b]:5060 SIP/2.0
    What is this device?
    What 3CX is essentially saying is that it does not know what this device is and does not know what to do with the call.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Ahmadi

    Joined:
    Sep 17, 2009
    Messages:
    10
    Likes Received:
    0
    My device is Cisco 5350.
    What mean "2" in "INVITE sip:2@10.45.20.17:5060 SIP/2.0" ?
    And i can not define "2" extension in 3CX because 3CX say me that extension must be atleast 3 characters!
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,567
    Likes Received:
    246
    Where are you routing your incoming calls, to a ring group, an extension, Digital receptionist? Did you define the trunk number (1000X) in your gateway?
     
  5. Ahmadi

    Joined:
    Sep 17, 2009
    Messages:
    10
    Likes Received:
    0
    To an extension.Its a SIP Client
    No,and I don't know how can i do that? Im not success to found any relative things with google ;)
    Thank you for your attention.
     
  6. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Here is a piece of information: http://wiki.3cx.com/documentation/voip-providers/how-to-solve-source-identification-issues

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Ahmadi

    Joined:
    Sep 17, 2009
    Messages:
    10
    Likes Received:
    0
    Hi
    After removing PSTN and adding a Voip Provider.
    My problem solved.
    But i don't know why?
    My cisco 5350 device is PSTN or Voip Provider?!

    Thank you for your attention.
     
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,567
    Likes Received:
    246
    The Cisco 5350 connects a VoIp PBX to the POTS network by a T1 or E1 carrier span, depending on which option you have. It isn't an analogue gateway and it wouldn't be used to connect to a VoIP provider. you would use it in the same way you would connect a "regular" PBX to a provider using PRI or carrier trunking.
     
  9. Ahmadi

    Joined:
    Sep 17, 2009
    Messages:
    10
    Likes Received:
    0
    I think im not success to explain my question, here is my question in another words:
    In my first try i used following steps:
    1) Configuring router Cisco 5350
    2) Installing 3CX and configuring it (Extensions,In/Out Rules, ...)
    3) Adding a gatway in "PSTN Devices" of 3CX management console with following information:
    IP: Ip of my gateway.
    Port: 5060
    And other information.
    4) Adding a DID and setupping "match any field" in source identification of the gateway.
    The above steps worked fine but im not success to catch incomming calls! and i started this topic in this forum that why i can not catch incomming calls.

    After very trys i used following steps:
    1) Configuring router Cisco 5350
    2) Installing 3CX and configuring it (Extensions,In/Out Rules, ...)
    3) Adding new provider in "Voip Providers" of 3CX management console as "Generic SIP trunk" with following information:
    SIP Server IP: Ip of my gateway.
    SIP Server Port: 5060
    And other information.
    4) Adding a DID and setting "match any field" in source identification of the provider.
    The above steps worked fine in both case (Incomming and Outcomming). and my problem solved fully.

    However, Im confusing that why the gatway settings as "PSTN" just worked in outcomming calls and can not catch incomming calls !?
    And why the gatway settings as "Generic SIP truck" voip provider work fine in both case? :shock:

    Thank you for any help
    H.Ahmadi
     
  10. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,567
    Likes Received:
    246
    I'm afraid that I'm not familiar with the Cisco to give a satisfactory answer to that. When you set up a SIP trunk, you have to put in the SIP server info so that 3CX can register with it. Does that mean that 3CX views the Cisco as a SIP server and not as a Gateway? I don't know.
     
Thread Status:
Not open for further replies.