9 Sep
2008
9 Sep
'08
2:40 p.m.
I'm having a problem with the route sections below. When SER receives an
Invite to proxy to a PSTN gateway, SER is sending 2 invites very fast to
the gateway in the first route block which ends up creating a mess with
the gateway.
Either I have something wrong in the routing code or I have an
SER/OS/hardware timing problem.
Any suggestions ?
route[1] {
xlog("L_INFO", "Sending to route 1\n%mb\n");
rewritehostport ("1.1.1.1:5060");
append_branch();
t_on_failure("1");
t_relay();
}
failure_route[1] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 1\n%mb\n");
append_branch();
route(2);
break;
}
route[2] {
xlog("L_INFO", "Sending to route 2\n%mb\n");
rewritehostport ("2.2.2.2:5060");
append_branch();
t_on_failure("2");
t_relay();
}
failure_route[2] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 2\n%mb\n");
append_branch();
route(3);
break;
}
route[3] {
xlog("L_INFO", "Sending to rout 3\n%mb\n");
rewritehostport ("3.3.3.3:5060");
t_relay();
}
Thanks,
Matt
9 Sep
9 Sep
4:27 p.m.
On Tue, Sep 9, 2008 at 8:40 PM, Matthew McGuire
<matthewmcguire(a)yahoo.com> wrote:
I'm having a problem with the route sections
below. When SER receives an
Invite to proxy to a PSTN gateway, SER is sending 2 invites very fast to the
gateway in the first route block which ends up creating a mess with the
gateway.
Either I have something wrong in the routing code or I have an
SER/OS/hardware timing problem.
Any suggestions ?
route[1] {
xlog("L_INFO", "Sending to route 1\n%mb\n");
rewritehostport ("1.1.1.1:5060");
append_branch();
t_on_failure("1");
t_relay();
}
failure_route[1] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 1\n%mb\n");
append_branch();
route(2);
break;
}
route[2] {
xlog("L_INFO", "Sending to route 2\n%mb\n");
rewritehostport ("2.2.2.2:5060");
append_branch();
t_on_failure("2");
t_relay();
}
failure_route[2] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 2\n%mb\n");
append_branch();
route(3);
break;
}
route[3] {
xlog("L_INFO", "Sending to rout 3\n%mb\n");
rewritehostport ("3.3.3.3:5060");
t_relay();
}
Please, delete append_branch() in route[1] and route[2].
By the way, in [a] you can find a complete configuration example--
terminating calls to a PSTN gateway is included (including PAI, RPID,
a.s.o.)
[a] http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg
Hope this helps,
--
Victor Pascual Ávila
5:23 p.m.
New subject: [Serusers] [Bulk] Re: failure route problem - duplicate invites
Thanks for the pointers.
When I remove append_branch from the route blocks, for some reason,
rewritehostport fails in subsequent routes. No errors show up in the
log, but the call will proceed through each block, traceable by the log
statements, but the host ip address on the new invites is the same as
the first invite.
ps. I am still on 0.9.6
matt
Victor Pascual Ávila wrote:
On Tue, Sep 9, 2008 at 8:40 PM, Matthew McGuire
<matthewmcguire(a)yahoo.com> wrote:
I'm having a problem with the route sections
below. When SER receives an
Invite to proxy to a PSTN gateway, SER is sending 2 invites very fast to the
gateway in the first route block which ends up creating a mess with the
gateway.
Either I have something wrong in the routing code or I have an
SER/OS/hardware timing problem.
Any suggestions ?
route[1] {
xlog("L_INFO", "Sending to route 1\n%mb\n");
rewritehostport ("1.1.1.1:5060");
append_branch();
t_on_failure("1");
t_relay();
}
failure_route[1] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 1\n%mb\n");
append_branch();
route(2);
break;
}
route[2] {
xlog("L_INFO", "Sending to route 2\n%mb\n");
rewritehostport ("2.2.2.2:5060");
append_branch();
t_on_failure("2");
t_relay();
}
failure_route[2] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 2\n%mb\n");
append_branch();
route(3);
break;
}
route[3] {
xlog("L_INFO", "Sending to rout 3\n%mb\n");
rewritehostport ("3.3.3.3:5060");
t_relay();
}
Please, delete append_branch() in route[1] and route[2].
By the way, in [a] you can find a complete configuration example--
terminating calls to a PSTN gateway is included (including PAI, RPID,
a.s.o.)
[a] http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg
Hope this helps,
11 Sep
11 Sep
5:37 p.m.
New subject: [Serusers] [Bulk] Re: [Bulk] Re: failure route problem - duplicate invites ---> incorrect o_uri
I finally got the failure routes working. For some reason, calling a
route block from a failure_route block caused rewritehostport to fail. I
got rid of that technique and now just cascade from failure_route[1] to
failure_route[2], etc. Works dandy.
However, now that I have calls routing properly, the acc table has the
wrong o_uri data. Instead of the successul uri from the failure_route,
the o_uri value in the acc table is being populated with the original
to_uri value.
Is there a fix for this? I'm on 0.9.6.
Thanks again for all the help.
Matt
Matthew McGuire wrote:
Thanks for the pointers.
When I remove append_branch from the route blocks, for some reason,
rewritehostport fails in subsequent routes. No errors show up in the
log, but the call will proceed through each block, traceable by the
log statements, but the host ip address on the new invites is the same
as the first invite.
ps. I am still on 0.9.6
matt
Victor Pascual Ávila wrote:
On Tue, Sep 9, 2008 at 8:40 PM, Matthew McGuire
<matthewmcguire(a)yahoo.com> wrote:
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers I'm having a problem with the route sections
below. When SER receives an
Invite to proxy to a PSTN gateway, SER is sending 2 invites very fast to the
gateway in the first route block which ends up creating a mess with the
gateway.
Either I have something wrong in the routing code or I have an
SER/OS/hardware timing problem.
Any suggestions ?
route[1] {
xlog("L_INFO", "Sending to route 1\n%mb\n");
rewritehostport ("1.1.1.1:5060");
append_branch();
t_on_failure("1");
t_relay();
}
failure_route[1] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 1\n%mb\n");
append_branch();
route(2);
break;
}
route[2] {
xlog("L_INFO", "Sending to route 2\n%mb\n");
rewritehostport ("2.2.2.2:5060");
append_branch();
t_on_failure("2");
t_relay();
}
failure_route[2] {
if(t_check_status("487")) {
break;
}
xlog( "L_INFO", "failure on route 2\n%mb\n");
append_branch();
route(3);
break;
}
route[3] {
xlog("L_INFO", "Sending to rout 3\n%mb\n");
rewritehostport ("3.3.3.3:5060");
t_relay();
}
Please, delete append_branch() in route[1] and route[2].
By the way, in [a] you can find a complete configuration example--
terminating calls to a PSTN gateway is included (including PAI, RPID,
a.s.o.)
[a] http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg
Hope this helps,
5952
days inactive
5954
days old
3 comments
2 participants
participants (2)
-
Matthew McGuire -
Victor Pascual Ávila