- Joined
- Oct 3, 2011
- Messages
- 4
- Reaction score
- 0
When making outbound calls the Route 1 field contains an unknown IP. I traced the IP and it's located in Pakistan. If I restart the 3CX PhoneSystem service it clears out the bad IP and start working like normal again. The problem will eventually come back but not always with the same IP, but always one that's registered in Pakistan.
Here how the route looks in the activity log:
10:56:23.445 [CM503004]: Call(891): Route 1: Unknown:12244011571@(Ln.10003@ISDN)@[Dev:sip:[email protected]:5066,Dev:sip:[email protected]:11342]
The 37.8.62.9 address is the Pakistan IP.
This is the first time that the bad IP has been in the last half of the route. It's usually in the first part and then all outbound calls are delayed about 20 seconds while it waits for the route to fail. Then it moves on the the second half and connects.
I've ran MalwareBytes and done a complete virus scan with Symantec Endpoint Security and found nothing.
Any thoughts how I can prevent this from continually happening?
Here how the route looks in the activity log:
10:56:23.445 [CM503004]: Call(891): Route 1: Unknown:12244011571@(Ln.10003@ISDN)@[Dev:sip:[email protected]:5066,Dev:sip:[email protected]:11342]
The 37.8.62.9 address is the Pakistan IP.
This is the first time that the bad IP has been in the last half of the route. It's usually in the first part and then all outbound calls are delayed about 20 seconds while it waits for the route to fail. Then it moves on the the second half and connects.
I've ran MalwareBytes and done a complete virus scan with Symantec Endpoint Security and found nothing.
Any thoughts how I can prevent this from continually happening?