Hi everyone,
I've been away from SER for a long time but now I have renewed interest.
I'm confronted by a problem I've failed to solve by my self, maybe you
could help, this is regarding accounting and what happens when a customer
responds with a 3xx response (i.e. redirect).
Call from customer to proxy works fine.
0(13212) Mon Feb 28 02:38:23 2005 - 130.244.194.233 - INVITE
Call-ID: 00036bc3-7aa519a2-610f6e63-7f1e22c2(a)130.244.194.233
From: sip:0856204081@sip-corporate1.testdomain.com
To: sip:0890510@sip-corporate1.testdomain.com
0(13212) Routeblock 2 - Calls from customers
0(13212) Call from customer: Test
0(13212) Call passed A-number check
0(13212) Routeblock 3 - To customer?
0(13212) Routeblock 4 - Call not to customer, to gateways
0(13212) Replyroute 1
0(13212) Replyroute 1
0(13212) Replyroute 1
0(13212) ACC: transaction answered: method=INVITE, uid=n/a,
call_id=00036bc3-7aa519a2-610f6e63-7f1e22c2(a)130.244.194.233,
from="0856204081"
<sip:0856204081@sip-corporate1.testdomain.com>;tag=00036bc37aa5007d581f01d7-0ea60293,
to=<sip:0890510@sip-corporate1.testdomain.com>;tag=18F3A96C-20F4,
i-uri=sip:0890510@sip-corporate1.testdomain.com,
o-uri=sip:0890510@sip-gw.swip.net:5060,
fromtag=00036bc37aa5007d581f01d7-0ea60293, code=200
0(13212) ACC: transaction answered: method=BYE, uid=n/a,
call_id=00036bc3-7aa519a2-610f6e63-7f1e22c2(a)130.244.194.233,
from="0856204081"
<sip:0856204081@sip-corporate1.testdomain.com>;tag=00036bc37aa5007d581f01d7-0ea60293,
to=<sip:0890510@sip-corporate1.testdomain.com>;tag=18F3A96C-20F4,
i-uri=sip:0890510@130.244.190.42:5060;ftag=00036bc37aa5007d581f01d7-0ea60293;lr=on,
o-uri=sip:0890510@130.244.188.14:5060,
fromtag=00036bc37aa5007d581f01d7-0ea60293, code=200
Accounting works fine with START, STOP
Call from PSTN to customer, works fine, I have choosen not to generate a
START record to make it easier for the billing department.
0(13212) Mon Feb 28 02:41:24 2005 - 130.244.188.14 - INVITE
Call-ID: 8CB1DEF-889B11D9-80F1FA83-930B318E(a)130.244.188.14
From: sip:0856264000@130.244.188.14
To: sip:0856204081@130.244.190.42
0(13212) Call from gateway
0(13212) Routeblock 3 - To customer?
0(13212) Call to customer: Test
0(13212) Replyroute 1
0(13212) Replyroute 1
0(13212) Replyroute 1
0(13212) ACC: transaction answered: method=BYE, uid=n/a,
call_id=8CB1DEF-889B11D9-80F1FA83-930B318E(a)130.244.188.14,
from=<sip:0856264000@130.244.188.14>;tag=18F66B24-226F,
to=<sip:0856204081@130.244.190.42>;tag=00036bc37aa5007f1d13f1ad-2475ba78,
i-uri=sip:0856204081@130.244.190.42:5060;ftag=18F66B24-226F;lr=on,
o-uri=sip:0856204081@130.244.194.233:5060, fromtag=18F66B24-226F, code=200
Here comes the tricky part.
Call from PSTN to customer and customer has redirected his extension to a
PSTN number.
0(13212) Mon Feb 28 02:42:49 2005 - 130.244.188.14 - INVITE
Call-ID: 3B95F3CB-889B11D9-80F5FA83-930B318E(a)130.244.188.14
From: sip:0856264000@130.244.188.14
To: sip:0856204081@130.244.190.42
0(13212) Call from gateway
0(13212) Routeblock 3 - To customer?
0(13212) Call to customer: Test
0(13212) Replyroute 1
0(13212) Redirect prohibited
This call generates no accounting (not even with setflag(1) at the top of
the route block)
I've managed to trigger the 'Redirect prohibited' message by using
onreply_route[] but I find no way of canceling the request there.
What I want is to be able to either disallow 3xx responses completly or
by selectivly cancelling them in onreply_route.
Another question, my ser-users archive just broke and I haven't been able
to do much searching, what's the best way today to handle several pstn
gateways and loadbalace between them for outgoing calls?
Best regards,
Thomas Björklund
Show replies by date
Thomas Björklund writes:
What I want is to be able to either disallow 3xx
responses completly or
by selectivly cancelling them in onreply_route.
if you use cisco gws, you can disallow 3xxs there.
-- juha
On Mon, 28 Feb 2005, Juha Heinanen wrote:
Thomas Björklund writes:
What I want is to be able to either disallow 3xx
responses completly or
by selectivly cancelling them in onreply_route.
if you use cisco gws, you can disallow 3xxs there.
-- juha
Thanks for the info, atleast I have a way of blocking it now, but it would
be nice to be able to disallow it earlier and also get an indication of
that a customer have a misconfigured pbx.
Best regards,
Thomas Björklund