[Kamailio-Users] Carrierrout issue

Ali Jawad ali.jawad at splendor.net
Tue Mar 3 16:52:16 CET 2009


 
Please check the attachemnt, each color is a asterisk server..all are
spiking together...what is missing is that there are no invite and bye
packets that are displayed and the ACC as well.




-----Original Message-----
From: Henning Westerholt [mailto:henning.westerholt at 1und1.de] 
Sent: 2009-03-03 16:54
To: users at lists.kamailio.org
Cc: Ali Jawad
Subject: Re: [Kamailio-Users] Carrierrout issue

On Tuesday 03 March 2009, Ali Jawad wrote:
> I do use carrieroute to balance calls to 3 servers and those 3 servers

> do use a2billing and they forward  calls to my pstn gw.

Hi Ali,

ok.

> I do have a
> graph that has the active calls on them randomly and it does not 
> depend on the load at hand the calls spike up on all 3 servers
together.

I don't understand you completly, sorry. :-) Can you perhaps rephrase
this a bit?

> And
> most of those calls are in ringing state but with no callerID.
> 
> Normally in the log for carrieroute I have something like this:
>
> Mar  3 13:39:10 [4288] INFO:carrierroute:cr_do_route: uri 
> xxxxxxxxxxxxx was rewritten to sip:xxxxxxxxxxxxxx
> ACC: transaction answered:
> timestamp=1236087551;method=INVITE;from_tag=rMciw2o;to_tag=as7761f5cf;
> ca
> ll_id=c745983c;code=200;reason=OK
> ACC: request acknowledged:
> timestamp=1236087551;method=ACK;from_tag=rMciw2o;to_tag=as7761f5cf;cal
> l_
> id=c745983c;code=200;reason=OK
> Mar  3 13:39:11 [4286] INFO:carrierroute:cr_do_route: uri 
> xxxxxxxxxxxxx was rewritten to sip:xxxxxxxxxxxxxxx Mar  3 13:39:12 
> [4287] INFO:carrierroute:cr_do_route: uri xxxxxxxxxxxx was rewritten 
> to sip:xxxxxxxxxxxxxx
> ACC: transaction answered:
> timestamp=1236087552;method=INVITE;from_tag=yJ+hSWA;to_tag=as26649b96;
> ca ll_id=a1c42904;code=183;reason=Session Progress
> ACC: transaction answered:
> timestamp=1236087552;method=INVITE;from_tag=CAJpAXg;to_tag=as5d24ff4f;
> ca ll_id=a35563d5;code=183;reason=Session Progress
> ACC: transaction answered:
> timestamp=1236087552;method=INVITE;from_tag=7i2kutG;to_tag=as6c125d0e;
> ca ll_id=2739b561;code=183;reason=Session Progress Mar  3 13:39:12 
> [4285] INFO:carrierroute:cr_do_route: uri xxxxxxxxxxxxxx was rewritten

> to sip:xxxxxxxxxxxxxxxxxx
> ACC: transaction answered:
> timestamp=1236087553;method=INVITE;from_tag=tMs9y8M;to_tag=as18b7f087;
> ca ll_id=7d65d34b;code=183;reason=Session Progress
>
>
> However when this problem happens the log screen only has the 
> something like the below and as said the calls are in ringing state 
> with no caller
> ID:
>
> Mar  3 13:39:11 [4286] INFO:carrierroute:cr_do_route: uri 
> xxxxxxxxxxxxx was rewritten to sip:xxxxxxxxxxxxxxx Mar  3 13:39:12 
> [4287] INFO:carrierroute:cr_do_route: uri xxxxxxxxxxxx was rewritten 
> to sip:xxxxxxxxxxxxxx

So you don't get accounting ("ACC:" lines) data for this calls? Is this
what missing? 

Cheers,

Henning




More information about the sr-users mailing list