Why does this happand ?

Discussion in '3CX Phone System - General' started by pstmg, Aug 14, 2014.

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

    Joined:
    Dec 9, 2012
    Messages:
    49
    Likes Received:
    0
    could you please tell me why this strange situation happands in 3 of our remote extensions ??


    14-08-2014 15:32:58.890 Leg L:7.1[Unknown:] is terminated: Cause: BYE from PBX
    14-08-2014 15:32:58.828 [CM502001]: Source info: From: "104"<sip:104@pbx-ip.org>;tag=e0c0cb9af082a005o0; To: <sip:103@pbx-ip.org>
    14-08-2014 15:32:58.828 [CM503013]: Call(C:7): Incoming call rejected, caller is unknown; msg=SipReq: INVITE 103@pbx-ip.org tid=-81f6b4b5 cseq=INVITE contact=104@remote-ip.org:5061 / 102 from(wire)
    14-08-2014 15:32:58.343 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    Invite-UNK Recv Req INVITE from remote-ip.org:5061 tid=-7b233c8d Call-ID=239a3efe-e7c723f1@192.168.1.2:
    INVITE sip:103@pbx-ip.org SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.2:5061;branch=z9hG4bK-7b233c8d;received=remote-ip
    Max-Forwards: 70
    Contact: "104"<sip:104@remote-ip.org:5061>
    To: <sip:103@pbx-ip.org>
    From: "104"<sip:104@pbx-ip.org>;tag=e0c0cb9af082a005o0
    Call-ID: 239a3efe-e7c723f1@192.168.1.2
    CSeq: 101 INVITE
    Expires: 240
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
    Content-Type: application/sdp
    Supported: x-sipura, replaces
    User-Agent: Linksys/PAP2-3.1.22(LS)
    Content-Length: 441

    It seems that calls from user 104 are being blocked due to unknown user. Why ?????????
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    My first guess is that you do not have pbx-ip.org set as the domain name in 3CX. For security reasons the call will be rejected from any source using that.
     
  3. pstmg

    Joined:
    Dec 9, 2012
    Messages:
    49
    Likes Received:
    0
    no i haven't registered ip-pbx.org. That address is just to mask the real ip of the 3CX server and the remote extension. It's strange but 104 can receive calls but can't make them. What could be happening ??

    but I do remember that when our dyndns provider had problems I changed domain name in the server and in some extentions. These 3 ware not changed.

    So if i have ip-pbx.org register in server and some remote extentions and other remote extentions have the domain ip-pbxs.org they can receive calls but are not allowed to make them ?????
     
  4. complex1

    complex1 Active Member

    Joined:
    Jan 25, 2010
    Messages:
    752
    Likes Received:
    38
    I think someone somehow hacked your PAP2.
    A few months ago I had the same.
    Replace the PAP2 for a other, non Linksys, ATA solves the issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. pstmg

    Joined:
    Dec 9, 2012
    Messages:
    49
    Likes Received:
    0
    they can hack this thing (pap2) behind a firewall ???
     
  6. pstmg

    Joined:
    Dec 9, 2012
    Messages:
    49
    Likes Received:
    0
    well I have to admit that today I've learned a little bit more: you're right leejor ! The problem was the domain name !!!


    thank you all very much for your help
     
Thread Status:
Not open for further replies.