2 May
2005
2 May
'05
4:31 p.m.
This is a hack, but:
You can redirect the REGISTER request to the 2nd server. SER-1 receives
a REGISTER and processes it with save_noreply(). It then redirects the
REGISTER method to the 2nd server using sl_send_reply("301", "Moved
Permamently"); The 2nd server will detect that the REGISTER has been
redirected and will generate 200 OK (a parameter in the request-uri
could be used for the detection).
If you set the expires to a short value (using max_expires parameter of
registrar module) than the user agent can keep NAT bindins open to both
servers.
Note:
1) The user agent has to support REGISTER/3xx (not all of them do)
2) I did not test this.
3) It really is a hack.
Jan.
On 02-05-2005 13:07, Andreas Granig wrote:
Juha Heinanen wrote:
the other option might be to make ser-1 to send
an options request to
uac-1 using ser-2's address in contact.
should have been "in via header".
How would you do this best?
Since the source address and the source port have to match SER-1's
address, IMHO you can't just use an external script to perform this
directly without SER-1, because you can't bind to SER-1's address.
If you inject the OPTIONS into SER-1 via FIFO or sipsak/sipp, the
request goes thru, but SER-1 adds it's address as topmost Via, so the
response always comes back to SER-1 first. Is it possible to suppress
the insertion of the own Via-Header?
Or even better: is there a way to send the OPTIONS from inside the
SER-Config without calling or using external scripts? Don't think so
(beside writing a module)...
Suggestions?
Andy
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers