Qualify=yes & Outboundproxy
I’m having some trouble turning with trunk monitoring while using an outbound proxy.
While all other sip messaging (e.g. calls) respects the outboundproxy setting, Options packets from setting qualify=yes do not. Asterisk tried to send the Options message directly to the “host=” IP, instead of the “outboundproxy=” IP as it should, verified with tcpdump.
I’ve done a search of the mailing list and didn’t turn up anything relevant. Is there a setting I’m missing, is this a bug, or just something that won’t work. It seemed appropriate to check here before I filed a bug report!
Best Regards, Nicholas Lemberger
5 thoughts on - Qualify=yes & Outboundproxy
Are you absolutely sure you need to use the outboundproxy setting rather than using a peer/friend?
—–Original Message—
I am sure I need outboundproxy 🙂
We use Kamailio in front of our softswitch as a type of firewall and because not all sip endpoints can set the headers such that they will work with said softswitch. Calling messages (and calling!) work just fine through the proxy – that setting just doesn’t seem to be honored by the qualify=yes messaging.
This isn’t a particular problem, but when we setup backup trunks that go through a different proxy, for redundancy without the monitoring, it takes a fair amount of time before the calls go through while it waits for the problem trunk to timeout on it’s own.
-Nick
We use opensips as a “type of firewall” as well and don’t need to set qualify=yes.
N
As I said, I don’t *need* to set qualify=yes for things to work. It’s just that trunk failover takes ~30 seconds. If the first/main trunk in an outbound route is down, outbound calls just sit with dead air for a ~30 second timeout before the next trunk in the outbound route is tried.
With qualify=yes, if the trunk is down, asterisk will mark it as such and will skip that trunk until it starts responding to the options ping again.
-Nick
As I said, I don’t *need* to set qualify=yes for things to work. It’s just that trunk failover takes ~30 seconds. If the first/main trunk in an outbound route is down, outbound calls just sit with dead air for a ~30 second timeout before the next trunk in the outbound route is tried.
With qualify=yes, if the trunk is down, asterisk will mark it as such and not try that trunk until it starts responding to the options ping again. Of course, the fact that it doesn’t seem to work properly is the problem.
-Nick