IPv6 SIP Phone: Moimstone IP215

So on the hunt to leave softphones behind, I went looking for a hardware phone that could work with IPv6. I found Moimstone based out of Korea. A lot of what they show online about their phones looked promising. Getting a phone proved to be a real challenge, and I had to rely on a co-worker to have his family in Korea order the phone, and then ship it to me here in California. I went with their entry level model, the IP215, which was also the cheapest 😉

So first things first with a phone on a network using DHCP, log into its webserver as the admin account. If you don’t read or speak Korean, stumble around the menus a bit to change the language setting. When you log in, you’ll see the phone’s network and SIP status:

Click on Phone Setup and then its sub-menu Network. You’ll see a check-box to enable IPv6, so go ahead and check that off:

After checking that off, the page will update and let you have IPv6 auto-configure, or you can set a static IPv6 address, prefix length, and gateway on the phone:

Scroll down to the bottom of the page and click on Save Settings. The phone will report that the configuration has been saved, and will take effect after the next reboot:

So click on the Maintenance tab, and reboot the phone.

After the phone has cycled and starts running the new configuration, you should see your IPv6 address in the phone’s status page:

Now you are ready to use SIP over IPv6. Obviously the next step is telling the phone what server to use. Click on the Call Setup tab and the Server sub-menu. Sadly you only get to specify IPv4 or IPv6 not both. So select the IPv6 radio button. One of the issues I noticed was that the phone didn’t like parsing IPv6 addresses, so I use a valid hostname for the server settings:

At this point, with valid user and server settings, and IPv6 enabled, the phone should be registering and able to take and make calls. One issue is that the phone doesn’t handle IPv6 literals in the address/hostname fields. This means it absolutely needs an IPv4 based recursor for performing DNS lookups.