I'd like to re-use the TCP connection UAs create with my registrar. I'd
like to send future SIP message along this existing connection,
particularly because I can't pierce NATs from the proxy server.
The sip outbound draft addresses this issue, but it requires the GRUU
extension. I like GRUU fine, but it's a pretty big change. I'm
wondering why you couldn't use something similar to the rport extension
to simply say "ignore the Contact header and use this connection"?
That's really all that's required. The stack implementation I'm using
(JAIN SIP) looks up connections according to IP/ports from the contact
header. You could just use a flag similar to rport to say "ignore the
IP/port in the contact header and use the IP/port for this connection
instead."
The only real reason you'd need to take this step is that you can't put
the correct port in the contact header if you create the message before
creating the TCP connection, since you won't know the ephemeral port
ahead of time. Now, granted, this is a bit of limitation to how JAIN
SIP is coded, but is there a simpler solution that just overwriting a
lot of code to set the contact header after the TCP connection is
established?
Thanks everyone.
-Adam
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
