SIP 301 Moved Permanently vs 439 First Hop Lacks Outbound Support
SIP 301 (Moved Permanently) is a 3xx Redirection response, while 439 (First Hop Lacks Outbound Support) 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, 439 means that the first outbound proxy does not support the SIP outbound mechanism (RFC 5626) that the UA is trying to use.
Descripción
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.
Cuándo lo verás
When a user has permanently changed their SIP address. All future calls should be directed to the new URI.
Cómo solucionarlo
Update your address book or routing tables to use the new Contact URI provided in the response.
Descripción
The first outbound proxy does not support the SIP outbound mechanism (RFC 5626) that the UA is trying to use.
Cuándo lo verás
When a UA configured for SIP outbound connects to a proxy that doesn't support the outbound option-tag.
Cómo solucionarlo
Upgrade the outbound proxy to support RFC 5626, or configure the UA to not require outbound support.
Diferencias clave
301 is a 3xx Redirection response, while 439 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 439: The first outbound proxy does not support the SIP outbound mechanism (RFC 5626) that the UA is trying to use.
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 439 when when a UA configured for SIP outbound connects to a proxy that doesn't support the outbound option-tag.
Cuándo usar cada uno
For 301 (Moved Permanently): Update your address book or routing tables to use the new Contact URI provided in the response. For 439 (First Hop Lacks Outbound Support): Upgrade the outbound proxy to support RFC 5626, or configure the UA to not require outbound support.