Cisco SPA962-NA Administration Guide - Page 27

SIP-NAT Interoperation, communications with the SIP entities outside the private network. - short name

Page 27 highlights

Chapter 1 Introducing Linksys 900 Series IP Phones Technology Background Step 2 Step 3 2. On the administration web server, System tab, set to the IP address and port number of your syslog server. Note that this address and port number has to be reachable from the SPA900 Series IP phone. 3. Set to 3, but do not change the value of the parameter. 4. To capture SIP signaling messages, under the Line tab, set to Full. The output is named syslog.514.log. To determine the type of NAT your router is using set to yes. View the syslog messages to determine if your network uses symmetric NAT. SIP-NAT Interoperation In the case of SIP, the addresses where messages/data should be sent to a 900 Series phone system are embedded in the SIP messages sent by the device. If the 900 Series phone system is sitting behind a NAT device, the private IP address assigned to it is not usable for communications with the SIP entities outside the private network. Note If the ITSP offers an outbound NAT-Aware proxy, this discovers the public IP address from the remote endpoint and eliminates the need to modify the SIP message from the UAC. The 900 Series phone system must substitute the private IP address information with the proper external IP address/port in the mapping chosen by the underlying NAT to communicate with a particular public peer address/port. For this, the 900 Series phone system must perform the following tasks: • Discover the NAT mappings used to communicate with the peer. This can be done with the help of an external device, such as a STUN server. A STUN server responds to a special NAT-Mapping-Discovery request by sending back a message to the source IP address/port of the request, where the message contains the source IP address/port of the original request. The 900 Series phone system can send this request when it first attempts to communicate with a SIP entity over the Internet. It then stores the mapping discovery results returned by the server. • Communicate the NAT mapping information to the external SIP entities. If the entity is a SIP Registrar, the information should be carried in the Contact header that overwrites the private address/port information. If the entity is another SIP UA when establishing a call, the information should be carried in the Contact header as well as in the SDP embedded in SIP message bodies. The VIA header in outbound SIP requests might also need to be substituted with the public address if the UAS relies on it to route back responses. • Extend the discovered NAT mappings by sending keep-alive packets. Because the mapping is alive only for a short period, the 900 Series phone system continues to send periodic keep-alive packets through the mapping to extend its validity as necessary. Document Version 3.0 Linksys 900 Series IP Phone Administrator Guide 1-13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164

1-13
Linksys 900 Series IP Phone Administrator Guide
Document Version 3.0
Chapter 1
Introducing Linksys 900 Series IP Phones
Technology Background
2.
On the administration web server, System tab, set <Debug Server> to the IP address and port number
of your syslog server.
Note that this address and port number has to be reachable from the SPA900 Series IP phone.
3.
Set <Debug level> to
3,
but do not change the value of the <syslog server> parameter.
4.
To capture SIP signaling messages, under the Line tab, set <SIP Debug Option> to
Full
. The output
is named syslog.514.log.
Step 2
To determine the type of NAT your router is using set <STUN Test Enable> to
yes
.
Step 3
View the syslog messages to determine if your network uses symmetric NAT.
SIP-NAT Interoperation
In the case of SIP, the addresses where messages/data should be sent to a
900 Series phone
system are embedded in the SIP messages sent by the device. If the 900 Series phone system
is sitting behind a NAT device, the private IP address assigned to it is not usable for
communications with the SIP entities outside the private network.
Note
If the ITSP offers an outbound NAT-Aware proxy, this discovers the public IP address from the remote
endpoint and eliminates the need to modify the SIP message from the UAC.
The
900 Series phone
system must substitute the private IP address information with the proper
external IP address/port in the mapping chosen by the underlying NAT to communicate with a
particular public peer address/port. For this, the
900 Series phone
system must perform the
following tasks:
Discover the NAT mappings used to communicate with the peer.
This can be done with the help of an external device, such as a STUN server. A STUN server
responds to a special NAT-Mapping-Discovery request by sending back a message to the source IP
address/port of the request, where the message contains the source IP address/port of the original
request. The
900 Series phone
system can send this request when it first attempts to communicate
with a SIP entity over the Internet. It then stores the mapping discovery results returned by the
server.
Communicate the NAT mapping information to the external SIP entities.
If the entity is a SIP Registrar, the information should be carried in the Contact header that
overwrites the private address/port information. If the entity is another SIP UA when establishing a
call, the information should be carried in the Contact header as well as in the SDP embedded in SIP
message bodies.
The VIA header in outbound SIP requests might also need to be substituted with
the public address if the UAS relies on it to route back responses.
Extend the discovered NAT mappings by sending keep-alive packets.
Because the mapping is alive only for a short period, the
900 Series phone
system continues to send
periodic keep-alive packets through the mapping to extend its validity as necessary.