SIP 301 Moved Permanently vs 302 Moved Temporarily
Both SIP 301 (Moved Permanently) and 302 (Moved Temporarily) belong to the 3xx Redirection category. 301 indicates that the user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header. Meanwhile, 302 means that the callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
Açıklama
The user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header.
Gördüğünüzde
When a user has permanently changed their SIP address. All future calls should be directed to the new URI.
Nasıl Düzeltilir
Update your address book or routing tables to use the new Contact URI provided in the response.
Açıklama
The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
Gördüğünüzde
When a user is temporarily reachable at a different location, such as when traveling or using a different device.
Nasıl Düzeltilir
Redirect the current call to the Contact URI provided, but keep the original URI for future requests.
Temel Farklar
SIP 301: The user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header.
SIP 302: The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
You encounter 301 when when a user has permanently changed their SIP address. All future calls should be directed to the new URI.
You encounter 302 when when a user is temporarily reachable at a different location, such as when traveling or using a different device.
Hangisini Ne Zaman Kullanmalı
For 301 (Moved Permanently): Update your address book or routing tables to use the new Contact URI provided in the response. For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests.