Is there any way to deal with a busy or out of service gateway? Would either of these situations activate a failure that we could use to change the route to a new gateway? If we set up the gateways in a huntgroup scenaro, and 2 or 3 failovers had to take place, what sort of delay could one expect?
Thanks,
Stephen
Subject: Re: [Serusers] Multiple SIP - PSTN Gateways
roughly like this:
if (uri=~"sip:972") { sethostport("dfw.nationalgateways.com"); } else if (uri=~"sip:911") { sethostport("emrgency.ngw.com"); } else { sethostport("defaultgw.com"); }; t_relay();
That's it. No guarantee for positioning of semicolons and other :$)"./... symbols.
-jiri
At 02:43 PM 9/25/2003, Wasik, Paul wrote:
Hi all,
Has anyone built a ser.cfg that can conditionally forward SIP calls to different SIP - PSTN gateways based on the outgoing calls area or
exchange
code. I'm sure it can be done but I'm not that good with syntax of the ser.cfg file. I know how to route to single SIP GW based on the dialed string but how do I make SER use multiple SIP gateways? Can anyone
provide
an example of this?
Thanks,
Paul
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
If a busy gateway sends a negative response than it could trigger a failure route. If the gateway is out of service then a timer could hit. Somebody has already asked similar question and I sent an example scripts (without testing !). Try to search the archive.
Jan.
On 03-10 11:15, Steve Dolloff wrote:
Is there any way to deal with a busy or out of service gateway? Would either of these situations activate a failure that we could use to change the route to a new gateway? If we set up the gateways in a huntgroup scenaro, and 2 or 3 failovers had to take place, what sort of delay could one expect?
Thanks,
Stephen
Subject: Re: [Serusers] Multiple SIP - PSTN Gateways
roughly like this:
if (uri=~"sip:972") { sethostport("dfw.nationalgateways.com"); } else if (uri=~"sip:911") { sethostport("emrgency.ngw.com"); } else { sethostport("defaultgw.com"); }; t_relay();
That's it. No guarantee for positioning of semicolons and other :$)"./... symbols.
-jiri
At 02:43 PM 9/25/2003, Wasik, Paul wrote:
Hi all,
Has anyone built a ser.cfg that can conditionally forward SIP calls to different SIP - PSTN gateways based on the outgoing calls area or
exchange
code. I'm sure it can be done but I'm not that good with syntax of the ser.cfg file. I know how to route to single SIP GW based on the dialed string but how do I make SER use multiple SIP gateways? Can anyone
provide
an example of this?
Thanks,
Paul
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hello,
I was looking for the same script at May 2003. You can find Jiri's and Jan's answers in the archive, the thread is "forwarding unanswered call - once more". Sorry, but I could not try the script, because the backup gateway was required for another project. I hope I will do it in some month.
I am also interesting in load balancing. Do you plan to extend the capabilities of SRV dns query? I mean supporting of multiple SRV records: load balancing in case of equal priority values, failover with different ones. Can this be a solution for both problem?
Miklos
Jan Janak wrote:
If a busy gateway sends a negative response than it could trigger a failure route. If the gateway is out of service then a timer could hit. Somebody has already asked similar question and I sent an example scripts (without testing !). Try to search the archive.
Jan.
On 03-10 11:15, Steve Dolloff wrote:
Is there any way to deal with a busy or out of service gateway? Would either of these situations activate a failure that we could use to change the route to a new gateway? If we set up the gateways in a huntgroup scenaro, and 2 or 3 failovers had to take place, what sort of delay could one expect?
Thanks,
Stephen
Subject: Re: [Serusers] Multiple SIP - PSTN Gateways
roughly like this:
if (uri=~"sip:972") { sethostport("dfw.nationalgateways.com"); } else if (uri=~"sip:911") { sethostport("emrgency.ngw.com"); } else { sethostport("defaultgw.com"); }; t_relay();
That's it. No guarantee for positioning of semicolons and other :$)"./... symbols.
-jiri
At 02:43 PM 9/25/2003, Wasik, Paul wrote:
Hi all,
Has anyone built a ser.cfg that can conditionally forward SIP calls to different SIP - PSTN gateways based on the outgoing calls area or
exchange
code. I'm sure it can be done but I'm not that good with syntax of the ser.cfg file. I know how to route to single SIP GW based on the dialed string but how do I make SER use multiple SIP gateways? Can anyone
provide
an example of this?
Thanks,
Paul
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
At 09:23 AM 10/8/2003, =?ISO-8859-2?Q?Tirp=E1k_Mikl=F3s?= wrote:
Hello,
I was looking for the same script at May 2003. You can find Jiri's and Jan's answers in the archive, the thread is "forwarding unanswered call - once more". Sorry, but I could not try the script, because the backup gateway was required for another project. I hope I will do it in some month.
I am also interesting in load balancing. Do you plan to extend the capabilities of SRV dns query? I mean supporting of multiple SRV records: load balancing in case of equal priority values, failover with different ones. Can this be a solution for both problem?
Embarassingly, we resolve SRV but don't retry if primary fails. We will implement it certainly, I am just not sure when is that going to be.
As for distributing load accross a gateway pool, it quite works with failure_route processing -- it gets us the ability to try again at some other place. It doesn't provide predefined distribution as it "amortizes" the first gateway, whereas backup gateway is only used when primary is unavailable or overloaded (501 or other negative reply coming back).
If one wanted to have a well-defined load-distribution scheme for a downstream gateway pool, DNS/SRV or a specialized module could be used -- I'm not yet sure which would be better off.
-jiri
-
Jan Janak -
Jiri Kuthan -
Steve Dolloff -
Tirpák Miklós