Why does this happand ?

[pstmg]

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:[email protected]>;tag=e0c0cb9af082a005o0; To: <sip:[email protected]>
14-08-2014 15:32:58.828 [CM503013]: Call(C:7): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=-81f6b4b5 cseq=INVITE [email protected]: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 [email protected]:
INVITE sip:[email protected] 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:[email protected]:5061>
To: <sip:[email protected]>
From: "104"<sip:[email protected]>;tag=e0c0cb9af082a005o0
Call-ID: [email protected]
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 ?????????

 

[leejor]

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.

 

[pstmg]

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 ?????

 

[complex1]

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.

 

[pstmg]

they can hack this thing (pap2) behind a firewall ???

 

[pstmg]

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