Re: [reSIProcate] Protocol decision?
On 10/11/05, Christian_Gavin@xxxxxxxxxxxx <Christian_Gavin@xxxxxxxxxxxx> wrote:
> Hi,
>
> Is there a callback that informs me about the protocol that reSIProcate
> chose after a successful NAPTR / SRV lookup ?
>
> According to the priorities in the SRV entries, TCP or UDP will be chosen.
> Depending on that:
>
> - I need to override the contact header field with my public IP address if
> using UDP (I will have discovered my public IP / port with STUN)
>
> - Don't override the contact header field if using TCP
>
> I need to know which protocol was chosen before the first REGISTER is sent,
> so I can decide to override the contact or not.
>
You can look at the Via in the response that comes back to you to find
out which transport was used. But you can't know before the REGISTER
goes out. You could send an OPTIONS and look at the Via in the
response before sending a REGISTER.
> Also, in the case of using TCP, does the contact header field have any
> meaning since I cannot run a NAT traversal algorithm with TCP ? Other than
> ";transport=tcp", the IP address in the Contact: header field is
> meaningless to the server, in my opinion (but required by RFCs anyway).
>
> Thanks,
> CG
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>