< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
So that's the fallback behavior that is specified. In practice, however, sending a bare IP address like that means that UDP will be attempted first, and if that fails for some reason (maybe a NAT is blocking UDP, for example), TCP will be attempted. The specifications are pretty muddy when it comes to transport failover, unfortunately. For sure, if a UA does not support TCP, it should be including a transport param to that effect. Now, as for solving your problem, I see a couple of approaches we could take;
1) Make greylisting configurable (enable/disable).
2) Make handling of sip:<bare-ip-addr> configurable (ie; is this a UDP-only URI, or is TCP a possible second candidate?) This basically boils down to disallowing multiple transport protocols for anything other than an FQDN.
Since both of these things are in grey areas of the specifications, both are reasonable things to make configurable. I like the second more, since it is more granular, and I am having a hard time coming up with a reasonable scenario where you'd want to disable greylisting for stuff you got from DNS. Your take?