IPKALL Does not ring

Discussion in '3CX Phone System - General' started by amygoda, Nov 7, 2012.

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

    amygoda Member

    Joined:
    Sep 18, 2006
    Messages:
    436
    Likes Received:
    0
    Hello,
    IPKALL setup to 3CX server ring group 81881 (2003 R2 SP2)
    the call did not ring



    12:28:46.440 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    INVITE sip:81881@172.17.99.201 SIP/2.0
    Via: SIP/2.0/UDP 66.54.140.46:5060;branch=z9hG4bK17f54493;rport=5060
    Max-Forwards: 70
    Contact: <sip:2066820185@66.54.140.46>
    To: <sip:81881@41.178.239.71>
    From: "unknown"<sip:2066820185@66.54.140.46>;tag=as4ec450da
    Call-ID: 5a5709fd0be97b1a43486c4e6516501d@66.54.140.46
    CSeq: 102 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
    Date: Wed, 07 Nov 2012 10:28:46 GMT
    Supported: replaces
    User-Agent: IPKall
    Content-Length: 0

    12:28:46.425 [CM302001]: Authorization system can not identify source of: SipReq: INVITE 81881@172.17.99.201 tid=17f54493 cseq=INVITE contact=2066820185@66.54.140.46 / 102 from(wire)
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    The incoming IP address (in your case 66.54.140.46) needs to be in the trunk settings for the IPKall trunk group you created in 3CX. Without it in there, 3CX thinks it is an attempted Direct SIP call and will reject it for security reasons.
     
Thread Status:
Not open for further replies.