![]() ![]() Law enforcement officials and collection agencies have been using the practice for years, sometimes in a legal way but oftentimes not. Phone number spoofing has been used for years by people with a specialized digital connection to the telephone company. Spoofing is usually done with malicious or unscrupulous motivations by the caller and it has led many people to believe that you can no longer trust Caller ID. While the caller’s information may appear local, the calls are often placed by telemarketers located outside the state or country. Phone number spoofing causes the Caller ID to display a phone number or other information to make it look like the calls are from a different person or business. But an increasingly common technique scam artists have been using is to falsify or “spoof” their caller ID information. Most phones have the ability to screen calls, providing information about the caller when the phone rings. Oh, Trung: If the extension is configured to hit the public IP whilst inside the LAN, the usual result is that the router will silently drop the packet (anti-spoofing).Unscrupulous telemarketers and scam artists are always looking for new ways to get people to answer their calls. If so, I suggest using that name, not the IP.Īlso, in addition to setting that name as the SIP server, set it as the Outbound Proxy as well. It seems a silly question, but are you able to ping the PABX using DNS name (ie ping )? From inside the LAN, and from the Internet? This assumes of course that you have control of the DNS (and know how to configure a split DNS). That way, if they’re inside the LAN, they work, if they’re out on the net, they work. With my own configuration, I’ve got all my extensions (at least, the ones that can) set to use the DNS name of the server. Of course, the configs ARE fairly self-documenting though… It’s a long time since I set mine up, and (like any good IT specialist) I didn’t thoroughly document it at the time. If so disable them until you get things working… The ONLY acception to that would be if you have any IPtables rules running on the box. Once you start getting info displayed via the sip debug you know your network is set right and then if it still does not connect properly it can be a server config issue. Next check all the other equipment that might be in between like a router. So please double check the firewall, make sure that the ports being forwarded are UDP, opening tcp ports are useless and potentially a security risk. If the traffic can’t get to the server then nothing you do at the server will fix that. Like I stated earlier that becomes a network/firewall/router issue. ![]() So when you hit it from the outside you are not seeing sip being info being displayed then it is NOT making it to the machine. So if you are not getting anything then you are NOT getting stuff forwarded. Sip debug will show ANY traffic that hit’s the sip port (5060). Most firewalls do not do/allow this (cisco pix and asa’s are the exception to that if the loopback option is enabled). When you are behind a firewall you can’t use the external IP as it would have to go out the firewall and loop back on the same interface. Nobody has asked if there is a firewall on the remote side? Sometimes port 5060 needs to be forwarded on that to the phone (older non-sip aware firewalls for example). I don’t know the firewall you are using it might not properly forward udp? So are you SURE you forwarded UDP ports and NOT TCP ports? as sip is a UDP based forwarding TCP ports will get you nowhere which is basically what you have now. That’s the problem with editing config files you are removing a important part of the info.īasically if the firewall is setup properly then packets would be forwarded to the asterisk box and you WOULD have output, since you have none the firewall is not forwarding properly. The sip_nat.conf looks with assuming the IP EDITED is the external IP of the firewall that has the ports being forwarded. But when the the phone is external it does not work then it is a firewall/router issue. If the phone works internal then the userID and password parts are right, the extension is configured correctly. I agree with bubba on this, it is a network/router issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |