VoIP no302: Difference between revisions

From AAISP Support Site
m (AA-Andrew moved page FireBrick VoIP no302 to VoIP no302)
mNo edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
SIP 302 is a 'Moved Temporarily' response from a SIP server to tell the client (the phone) to go and register against a different SIP server. This is useful to help direct phones to the correct SIP server and to help load balance servers and so on.
SIP 302 is a 'Moved Temporarily' response from a SIP server to tell the client (the phone) to go and register against a different SIP server. This is useful to help direct phones to the correct SIP server and to help load balance servers and so on.


The Message is defined in [[https://tools.ietf.org/html/rfc3261#section-21.3.3|RFC 3261]], but unfortunately not all SIP clients support it.
The Message is defined in [https://tools.ietf.org/html/rfc3261#section-21.3.3 RFC 3261], but unfortunately not all SIP clients support it.


FireBrick SIP supports this, both as a server and a client.
FireBrick SIP supports this, both as a server and a client.


==Use Within the AAISP VoIP Platform==
==Use Within the AAISP VoIP Platform==
AAISP use this feature to enable the service to be load-balanced across multiple SIP servers, however, if your client (phone) does not support this feature then you can use the sevrer name no302.voiceless.aa.net.uk. Please do report this to the manufacturer.
AAISP was going to use feature to enable the service to be load-balanced across multiple SIP servers, however, as support for this was limited/broken in many devices it is not being used. AAISP are still balancing traffic over multiple servers.


=Does Not Support 302=
*freeswitch 1.2.10



=Does Support 302=
*SNOM
*FireBrick




[[Category:VoIP]]
[[Category:VoIP]]
[[Category:FireBrick]]

Latest revision as of 12:18, 31 July 2013

SIP 302 is a 'Moved Temporarily' response from a SIP server to tell the client (the phone) to go and register against a different SIP server. This is useful to help direct phones to the correct SIP server and to help load balance servers and so on.

The Message is defined in RFC 3261, but unfortunately not all SIP clients support it.

FireBrick SIP supports this, both as a server and a client.

Use Within the AAISP VoIP Platform

AAISP was going to use feature to enable the service to be load-balanced across multiple SIP servers, however, as support for this was limited/broken in many devices it is not being used. AAISP are still balancing traffic over multiple servers.