Free SIP Phone for Windows, Web, Android and iOS – 3CX Apps. 3CX’s open-standards PBX offers powerful apps for the Web, Windows, iOS and Android. With the free VoIP softphone, use your extension from anywhere with no additional cost and increase your productivity and mobility. The benefits of the 3CX App are many and are broken down in more. MicroSIP is a portable SIP softphone based on the PJSIP stack available for Microsoft Windows operating systems. It facilitates high quality VoIP calls (p2p or on regular telephones) based on the open SIP protocol. Poly Studio X50. Poly Studio X family Video Bars deliver radical simplicity in a single sleek device. Now you can huddle happy in smaller rooms and connect easy in conference rooms whatever video collaboration software you use. Let’s say you have the MAC address 60-30-d4-76-b8-c8 (which is a macOS device) and you want to know the IP. From the results shown above, you can map the MAC address to the IP address in the same line. The IP Address is 192.168.0.102 (which is in the same network segment) belongs to 60-30-d4-76-b8-c8.
IPhone SIP Client 2.0 for Mac is available as a free download on our application library. Our antivirus analysis shows that this Mac download is malware free. The software is categorized as Communication Tools.
How would you communicate with a device when you don’t have the IP?
You might be in a situation where you don’t have the IP address of a device in a local network, but all you have is records of the MAC or hardware address.
Or your computer is unable to display its IP due to various reasons, and you are getting a “No Valid IP Address” error.
Finding the IP from a known MAC address should be the task of a ReverseARP application, the counterpart of ARP.
But RARP is an obsolete protocol with many disadvantages, so it was quickly replaced by other protocols like BOOTP and DHCP, which deal directly with IP addresses.
In this article, we’ll show you how to find IPs and device vendors using MAC addresses with different methods for free.
Understanding ARP
ARP (Address Resolution Protocol) is the protocol in charge of finding MAC addresses with IPs in local network segments.
It operates with frames on the data link layer.
As you might already know, devices in the data link layer depend on MAC addresses for their communication.
Their frames encapsulate packets that contain IP address information.
A device must know the destination MAC address to communicate locally through media types like Ethernet or Wifi, in layer 2 of the OSI model.
Merlin Project for Mac. With customizable reports, Merlin Project allows any time an overview of the utilization of staff, budget and the state of the project progress. Merlin project for mac. Merlin Project For the Mobile Project Manager. With the flagship of our products you plan and organize projects of any size - in the office, on the road and remotely from home. Lone fighters and teams love the intuitive operation and effortless data synchronization between all their devices. Conveniently, Merlin Project comes ready to integrate with OS X apps like iCal, Contacts (and more), open interfaces to other Mac programs, and the possibility to import data from the Microsoft (e.g. Excel and MS Project) — which ProjectWizards considers to be important for Mac users to work efficiently. Merlin Project is the industry standard for project management on macOS and iOS. Clients from various industries work with Merlin Project and love it for its ease of use and scalability. Merlin Project is the standard for project management in industries such as Architecture & Construction, Media & Agencies, Research & Development, Education and others. For more than 15 years customers in over 150 countries have been using our flexible app to plan, manage & control their small and large projects.
Understanding how ARP works can help you find IPs and MAC addresses quickly.
The following message flow diagram can help you understand the concept:
- The local computer sends a ping (ICMP echo request) to a destination IP address (remote computer) within the same segment. Unfortunately, the local computer does not know the MAC address… it only knows the IP address.
- The destination hardware address is unknown, so the ICMP echo request is put on hold. The local computer only knows its source/destination IP and its source MAC addresses. ARP uses two types of messages, ARP Request and Reply.
The local computer sends an ARP REQUEST message to find the owner of the IP address in question.
This message is sent to all devices within the same segment or LAN through a broadcast MAC (FF:FF:FF:FF:FF:FF) as the destination.
- Because the remote computer is part of the same network segment, it receives the broadcast message sent by the local computer. All other computers in the LAN also receive the broadcast but they know that the destination IP is not theirs, so they discard the packet. Only the remote computer with destination IP, responds to the ARP REQUEST with an ARP REPLY, which contains the target MAC address.
- The local computer receives the ARP REPLY with the MAC address. It then resumes the ICMP echo request, and finally, the remote computer responds with an ICMP echo reply.
Finding IPs with ARP
You can use ARP to obtain an IP from a known MAC address.
But first, it is important to update your local ARP table in order to get information from all devices in the network.
Send a ping (ICMP echo reply) to the entire LAN, to get all the MAC entries on the table.
To ping the entire LAN, you can send a broadcast to your network.
Open the Command Prompt in Windows or terminal in macOS and type.
ping 192.168.0.255
My subnet is 192.168.0.0/24 (mask of 255.255.255.0), so the broadcast address is 192.168.0.255 which can be calculated or found with a “Print Route” command in Windows or a “netstat -nr” in macOS. Or can also be obtained with a subnet calculator.
For Windows:
Step 1.
- Open the CMD (Command Prompt)
- Go to the “Start” menu and select “Run” or press (Windows key + R) to open the Run application
- In the “Open” textbox type “cmd” and press “Ok”.
This will open the command-line interface in Windows.
Step 2.
- Enter the “arp” command.
- The arp command without any additional arguments will give you a list of options that you can use.
Step 3.
- Use the arp with additional arguments to find the IP within the same network segment.
- With the command “arp -a” you can see the ARP table and its entries recently populated by your computer with the broadcast ping.
Step 4.
- Reading the output.
- The information displayed in the arp-a is basically the ARP table on your computer.
- It shows a list with IP addresses, their corresponding physical address (or MAC), and the type of allocation (dynamic or static).
Let’s say you have the MAC address 60-30-d4-76-b8-c8 (which is a macOS device) and you want to know the IP.
From the results shown above, you can map the MAC address to the IP address in the same line.
The IP Address is 192.168.0.102 (which is in the same network segment) belongs to 60-30-d4-76-b8-c8.
You can forget about those 224.0.0.x and 239.0.0.x addresses, as they are multicast IPs.
For macOS:
Step 1:
- Open the Terminal App. go to Applications > Utilities > Terminal or Launchpad > Other > Terminal.
Step 2:
- Enter the “arp” command with an “-a” flag.
- Once you enter the command “arp -a” you’ll receive a list with all ARP entries to the ARP Table in your computer.
- The output will show a line with the IP address followed by the MAC address, the interface, and the allocation type (dynamic/static).
Finding IPs with the DHCP Server
The Dynamic Host Configuration Protocol (DHCP) is the network protocol used by TCP/IP to dynamically allocate IP addresses and other characteristics to devices in a network.
The DHCP works with a client/server mode.
The DHCP server is the device in charge of assigning IP addresses in a network, and the client is usually your computer.
For home networks or LANs, the DHCP Server is typically a router or gateway.
If you have access to the DHCP Server, you can view all relationships with IPs, MACs, interfaces, name of the device, and lease time in your LAN.
Step 1.
- Log into the DHCP Server. In this example, the DHCP server is the home gateway.
- If you don’t know the IP address of your DHCP Server/ Gateway, you can run an ipconfig (in Windows) or ifconfig (in macOS/Linux).
- This particular DHCP Server/Gateway has a web interface.
Step 2.
- Enter the IP address on the search bar of the web browser, and input the right credentials.
Step 3.
- Find the DHCP Clients List.
- In this TP-Link router, the DHCP Server functionality comes as an additional feature.
- Go to DHCP > DHCP Clients List. From this list, you can see the mapping between MAC addresses and their assigned IPs.
Using Sniffers
If you couldn’t find the IP in the ARP list or unfortunately don’t have access to the DHCP Server, as a last resort, you can use a sniffer.
Packet sniffers or network analyzers like Nmap (or Zenmap which is the GUI version) are designed for network security.
They can help identify attacks and vulnerabilities in the network.
With Nmap, you can actively scan your entire network and find IPs, ports, protocols, MACs, etc.
If you are trying to find the IP from a known MAC with a sniffer like Nmap, look for the MAC address within the scan results.
How to find the Device and IP with a Sniffer?
Step 1.
- Keep records of your network IP address information.
- In this case, my network IP is 192.168.0.0/24. If you don’t know it, a quick “ipconfig” in Windows cmd or an “ifconfig” in macOS or Linux terminal can show you the local IP and mask.
- If you can’t subnet, go online to a subnet calculator and find your network IP.
Step 2.
- Download and open Nmap.
- Download Nmap from this official link https://nmap.org/download.html and follow its straightforward installation process.
Step 3.
- Open Nmap (or Zenmap) and use the command “sudo nmap -sn (network IP)” to scan the entire network (without port scan).
- The command will list machines that respond to the Ping and will include their MAC address along with the vendor.
- Don’t forget the “sudo” command.
- Without it, you will not see MAC addresses.
Finding out the device vendor from a MAC address
Ok, so now you were able to find out the IP address using “arp -a” command or through the DHCP Server.
But what if you want to know more details about that particular device?
What vendor is it?
Your network segment or LAN might be full of different devices, from computers, firewalls, routers, mobiles, printers, TVs, etc.
And MAC addresses contain key information for knowing more details about each network device.
First, it is essential to understand the format of the MAC address.
Traditional MAC addresses are 48 bits represented in 12-digit hexadecimal numbers (or six octets).
The first half of the six octets represent the Organizational Unique Identifier (OUI) and the other half is the Network Interface Controller (NIC) which is unique for every device in the world.
There is not much we can do about the NIC, other than communicating with it.
But the OUI can give us useful information about the vendor if you didn’t use Nmap, which can also give you the hardware vendor.
A free online OUI lookup tool like Wireshark OUI Lookup can help you with this.
Just enter the MAC address on the OUI search, and the tool will look at the first three octets and correlate with its manufacturing database.
Final Words
Although the RARP (the counterpart of ARP) was specifically designed to find IPs from MAC addresses, it was quickly discontinued because it had many drawbacks.
RARP was quickly replaced by DHCP and BOOTP.
But ARP is still one of the core functions of the IP layer in the TCP/IP protocol stack.
It finds MAC addresses from known IPs, which is most common in today’s communications.
ARP works under the hood to keep a frequently used list of MACs and IPs.
But you can also use it to see the current mappings with the command arp -a.
Aside from ARP, you can also use DHCP to view IP information. DHCP Servers are usually in charge of IP assignments.
If you have access to the DHCP server, go into the DHCP Client list and identify the IP with the MAC address.
Finally, you can use a network sniffer like Nmap, scan your entire network, and find IPs, and MACs.
If you only want to know the vendor, an online OUI lookup like Wireshark can help you find it quickly.
CUCM supports RFC 3261-compliant third-party SIP phones. Support for third-party SIP phone features varies greatly from Cisco SIP IP Phone features. Third-party phones have only RFC 3261 SIP Version 2 support, whereas Cisco SIP Phones have many Cisco SCCP features that have been rewritten to work in a native SIP protocol stack.
Two different types of third-party SIP phones can be added to CUCM. Third-party SIP phones may be added as basic or advanced phones. Third-party SIP basic phones support one line appearance and consume three DLUs. Third-party SIP advanced phones support up to eight lines and video but consume six DLUs. Basic and advanced third-party SIP phones offer the same telephony features.
Third-party SIP phones register with CUCM but do not use a MAC address-based device ID. CUCM uses SIP digest authentication to identify a registering SIP third-party SIP phone.
Both CUCM and the third-party SIP phone have to be configured with a username and password for digest authentication to work properly. CUCM refers to this item as a digest user in which a user is associated with the phone in both the phone and user configuration pages. The third-party device must also be configured with a matching username.
SIP standards and drafts supported by CUCM include the following:
RFC | 3262: | PRACK |
RFC | 3264: | SDP offer/answer |
RFC | 3311: | UPDATE |
RFC | 3515: | REFER |
RFC | 3842: | MWI Package |
RFC | 3891: | Replaces Header |
RFC | 3892: | Referred-by Mechanism |
■ draft-levy-sip-diversion-08.txt: Diversion Header
■ draft-ietf-sip-privacy-04.txt: Remote-Party-Id Header
The following audio and video standards are supported for third-party SIP phones:
—Audio codecs: G.711 mu-law, GSM Full-rate, G.723.1, G.711 A-law, G.722, G.728, G.729
—RFC 2833: DTMF (Telephony-event)
—Video codecs: H.261, H.263, H.263+, H.263++, H.264
NOTE For more information about the support of these standards, see the Cisco SIP IP Administrator Guide, Version 8.0 - Compliance with RFC 3261:
Cisco is working with key third-party vendors who are part of the Cisco Technology Development Partner Program. These partners are developing solutions that leverage the new CUCM and CUCM Express SIP capabilities. These vendors include Linksys, IPCelerate, Research In Motion, IP blue, and Grandstream.
Cisco is also participating in an independent third-party testing and interoperability verification process being offered by tekVizion. This independent service has been established to enable third-party vendors to test and verify the interoperability of their endpoints with CUCM and CUCM Express.
Third-party SIP phones support only a few features compared to Cisco IP Phones using SCCP or SIP. The features that are not supported include but are not limited to the following:
■ MAC address registration
Sip Phone For Mac Pro
■ Phone buttons template
■ Soft key templates
Best Sip Client For Macos
■ Telephony features and applications such as the following:
—IP phone services
—CUCM Assistant
Download Sip Phone For Mac
—Cisco Unified Video Advantage
—Call Pickup
—Presence
SIP Third-Party Authentication
Digest authentication allows CUCM to act as a server to challenge the identity of a SIP device when it sends a request to CUCM. When digest authentication is enabled for a phone, CUCM challenges all SIP phone requests except keepalive messages. CUCM does not support responding to challenges from SIP phones.
CUCM can challenge SIP devices connecting through a SIP trunk and can respond to challenges received on its SIP trunk interface.
CUCM digest authentication is used to determine the identity of a third-party SIP phone. The phones cannot be authenticated via MAC address like SCCP devices because third-party SIP phones do not register by MAC address. Digest authentication is the industry standard.
CUCM can ignore the keyed hash that is provided in a digest authentication response and check only if the provided username exists and is bound to a third-party SIP phone. This is the default behavior. Alternatively, CUCM can be configured to check that the key that was used at the third-party SIP phone to generate the keyed hash matches the locally configured key (called digest credentials) at the end-user configuration in CUCM.
Third-party SIP phones cannot be configured by using the CUCM TFTP server. Instead, they need to be configured using the native phone configuration mechanism, which is usually a web page or a TFTP file. The device and line configuration in the CUCM database must be manually synchronized with the native phone configuration (for example, extension 1002 on the phone and 1002 in CUCM). In addition, if the directory number of a line is changed, it must be changed in both CUCM Administration and in the native phone configuration mechanism.
Third-party SIP phones include their directory number in the registration message. They do not send a MAC address. Third-party SIP phones identify themselves with digest authentication. The SIP REGISTER message includes a header with a username and the keyed hash, as shown in the following example:
Authorization: Digest username='3rdpsip' ,realm='ccmsipline',nonce='GBauADss2qoWr6k9y3hGGVDAqnl_fol_k5', uri='sip:172.18.197.224',algorithm=MD5,response='126c0643a4923359ab59d4f5349455 2e'
CUCM receives the registration message and searches for an endpoint that matches the provided username in the SIP message (3rdpsip in the preceding example). CUCM uses the digest credentials configured for that user to verify the keyed hash (response='126c0643a4923359ab59d4f53494552e in the preceding example).
NOTE CUCM must be explicitly configured to verify the keyed hash. By default, CUCM searches only for the end-user name.
CUCM searches for a third-party SIP phone that is associated with the end user and verifies that the configured directory number matches the one provided by the third-party SIP phone in its registration message. If the phone is found and the directory number is the same, the third-party SIP phone registers with CUCM.
To add a third-party SIP phone in CUCM, follow these steps:
Step 1 Configure an end user in CUCM and specify the digest credentials.
Step 2 Add the third-party SIP phone in CUCM and configure its directory number.
NOTE When you are configuring the third-party SIP phone in CUCM, a dummy MAC address can be specified. The MAC address is not used to identify the device but is required inside the CUCM configuration database.
Step 3 Associate the third-party SIP phone with the end user.
Step 4 Configure the third-party SIP phone with the IP address of the CUCM, end-user ID, digest credentials, and directory number.
Best Sip Client For Mac
Was this article helpful?