Networking/IPv6
From Snom User Wiki
Contents |
Introduction
UPDATE: IPv6 is now supported in all stable 8.7.5 releases, with some exceptions (snom300/320/360/370/710, PA1, Meetingpoint). For more information, please read the Release Notes for new firmware releases. Current Release (Nov. 2015): FW 8.7.5.35 Release Notes and Download Links.
We are delighted to announce that snom is now close to releasing IPv6-capable firmware.
A BETA version is currently available here.
The firmware is available for snom8xx and 7xx phones. snom3xx, PA1 and Meetingpoint are not supported due to technical limitations.
Please find below an overview of how to set up IPv6 on your phone. Frequently asked questions are answered here.
If you want to know more about IPv6, snom has also created a white paper to introduce you to it. It can be found here.
If you discover a bug or require further support, please feel free to post in the special IPv6 area of the snom forum.
Using IPv6
Note: Before 8.7.5.35 Release, it was only supported in the BETA version 8.7.5.8
- In order to use the IPv6 mode, you need to go to the advanced settings and click on More Controls next IPv6.
- Now you need to choose between autoconfiguration or on.
- Autoconfiguration means: Only SLAAC (Stateless Address AutoConfiguration is enabled)
- On means: DHCPv6 and SLAAC is enabled
- Now you need to save the changes and reboot your phone:
- During bootup you should notice that the phone also acquired an IPv6 address:
- Now you can open the phone’s webinterface via IPv6:
- Under the tab Identity you can enter your credentials and an IPv6 enabled SIP-server:
Examples
Registration
In the SIP-Trace you can monitor the registration process:
Sent to udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:216 (833 bytes): REGISTER sip:ipv6.sip.easybell.de SIP/2.0 Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-4r8raqapbbeu;rport From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de> Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 11 REGISTER Max-Forwards: 70 User-Agent: snom760/8.7.5.201307040244-OCS Contact: <sip:00493098323521@[2001:6f8:900:900e:204:13ff:fe71:a37]:58517;line=33zyx3c4>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:cc5c375d- 88be-4592-8236-000413710A37>";audio;mobility="fixed";duplex="full";description="snom760";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO" Allow-Events: dialog X-Real-IP: [2001:6f8:900:900e:204:13ff:fe71:a37] Supported: path, gruu Content-Length: 0 Received from udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:269 (348 bytes): SIP/2.0 100 Trying Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-4r8raqapbbeu;rport=58517 From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de> Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 11 REGISTER Server: Sipwise NGCP Proxy 2.X Content-Length: 0 Received from udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:274 (493 bytes): SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-4r8raqapbbeu;rport=58517 From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.139b Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 11 REGISTER WWW-Authenticate: Digest realm="ipv6.sip.easybell.de", nonce="UlU3N1JVNgt1myZHQ7b7rGO2IFfJ8mPs" Server: Sipwise NGCP Proxy 2.X Content-Length: 0 Sent to udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:283 (1041 bytes): REGISTER sip:ipv6.sip.easybell.de SIP/2.0 Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-6pi2dnd5eovo;rport From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de> Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 12 REGISTER Max-Forwards: 70 User-Agent: snom760/8.7.5.201307040244-OCS Contact: <sip:00493098323521@[2001:6f8:900:900e:204:13ff:fe71:a37]:58517;line=33zyx3c4>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:cc5c375d-88be-4592-8236-000413710A37>";audio;mobility="fixed";duplex="full";description="snom760";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO" Allow-Events: dialog X-Real-IP: [2001:6f8:900:900e:204:13ff:fe71:a37] Supported: path, gruu Authorization: Digest username="00493098323521",realm="ipv6.sip.easybell.de",nonce="UlU3N1JVNgt1myZHQ7b7rGO2IFfJ8mPs",uri="sip:ipv6.sip.easybell.de",response="214a3863c40ad33e5345077463b86803",algorithm=MD5 Content-Length: 0 Received from udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:329 (348 bytes): SIP/2.0 100 Trying Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-6pi2dnd5eovo;rport=58517 From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de> Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 12 REGISTER Server: Sipwise NGCP Proxy 2.X Content-Length: 0 Received from udp:[2001:4090:4008::124]:5060 at 9/10/2013 12:55:07:335 (739 bytes): SIP/2.0 200 OK Via: SIP/2.0/UDP [2001:6f8:900:900e:204:13ff:fe71:a37]:58517;branch=z9hG4bK-6pi2dnd5eovo;rport=58517 From: <sip:00493098323521@ipv6.sip.easybell.de>;tag=hnz9km7ons To: <sip:00493098323521@ipv6.sip.easybell.de>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.23d7 Call-ID: 038ec3d6a4984e7a8e79a3bb093052aa CSeq: 12 REGISTER Contact: <sip:00493098323521@[2001:6f8:900:900e:204:13ff:fe71:a37]:58517;line=33zyx3c4>;q=1;expires=600;pub-gruu="sip:00493098323521@ipv6.sip.easybell.de;gr=urn:uuid:cc5c375d-88be-4592-8236-000413710A37";temp-gruu="sip:uloc-52389715-6a09-45af3a-31f3af0a@ipv6.sip.easybell.de;gr";+sip.instance="<urn:uuid:cc5c375d-88be-4592-8236-000413710A37>";reg-id=1 Server: Sipwise NGCP Proxy 2.X Content-Length: 0
IPv6 on the PC port
Even if your phone is using an IPv4 address, you can connect a IPv6 host on the PC port. The phone acts only as a switch from PC to NET port. This means that if the host sends IPv6 packets to the phone on the PC port, the packets are sent further through the NET port of the phone, with no change to the IP headers.
IPv6 on snom m9
The snom m9 natively supports IPv6 for SIP. Please see the configuration and usage details here