SIP 301 Moved Permanently vs 436 Bad Identity-Info
SIP 301 (Moved Permanently) is a 3xx Redirection response, while 436 (Bad Identity-Info) is a 4xx Client Failure response. 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. In contrast, 436 means that the Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
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 Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
Gördüğünüzde
When the Identity-Info URI in the request points to an unreachable or invalid certificate location.
Nasıl Düzeltilir
Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.
Temel Farklar
301 is a 3xx Redirection response, while 436 is a 4xx Client Failure response.
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 436: The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
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 436 when when the Identity-Info URI in the request points to an unreachable or invalid certificate location.
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 436 (Bad Identity-Info): Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.