24 Feb
2006
24 Feb
'06
4:48 a.m.
I'm doing an interop test with a well known
ITPS, they are kicking back these BYE retransmits, like:
SIP MESSAGE 18 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 18 17/Feb/06 17:09:36.8142
TimeFromPreviousSipFrame=0.0010 TimeFromStart=8.0692
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
SIP MESSAGE 19 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 19 17/Feb/06 17:09:36.8424
TimeFromPreviousSipFrame=0.0282 TimeFromStart=8.0974
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
Why is the BYE being sent so quickly?
This is an intermediate UAS proxy, and every now and
then it spits out an extra BYE like this. Shouldn't
this wait 500ms before doing a retry? The rest of the trace
is clean. I can forward the whole thing if there is any interest.
-g
--
Greg Fausak
greg(a)thursday.com
24 Feb
24 Feb
8:34 a.m.
Hello Greg,
the issue comes from the internal timer of openser, it has a fidelity of
one seconds, so for the first retransmission it might be under 500ms.
Does this issue cause troubles? We are looking to an alternative to
improve the timer in this respect, but no timeline at this moment.
Cheers,
Daniel
On 02/23/06 19:48, Greg Fausak wrote:
I'm doing an interop test with a well known
ITPS, they are kicking back these BYE retransmits, like:
SIP MESSAGE 18 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 18 17/Feb/06 17:09:36.8142
TimeFromPreviousSipFrame=0.0010 TimeFromStart=8.0692
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
SIP MESSAGE 19 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 19 17/Feb/06 17:09:36.8424
TimeFromPreviousSipFrame=0.0282 TimeFromStart=8.0974
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
Why is the BYE being sent so quickly?
This is an intermediate UAS proxy, and every now and
then it spits out an extra BYE like this. Shouldn't
this wait 500ms before doing a retry? The rest of the trace
is clean. I can forward the whole thing if there is any interest.
-g
--
Greg Fausak
greg(a)thursday.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
8:50 a.m.
Daniel,
I see now. You are using alarm() call?
I think it would be better for the first timeout to be more than a second.
We are seeing initial timeouts in the 30ms range...some of the
big boys don't like it. Can't I set the t1 timeout individually?
I'll try setting it
to 2 :-)
-g
On 2/23/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello Greg,
the issue comes from the internal timer of openser, it has a fidelity of
one seconds, so for the first retransmission it might be under 500ms.
Does this issue cause troubles? We are looking to an alternative to
improve the timer in this respect, but no timeline at this moment.
Cheers,
Daniel
On 02/23/06 19:48, Greg Fausak wrote:
--
Greg Fausak
greg(a)thursday.com
I'm doing an interop test with a well known
ITPS, they are kicking back these BYE retransmits, like:
SIP MESSAGE 18 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 18 17/Feb/06 17:09:36.8142
TimeFromPreviousSipFrame=0.0010 TimeFromStart=8.0692
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
SIP MESSAGE 19 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 19 17/Feb/06 17:09:36.8424
TimeFromPreviousSipFrame=0.0282 TimeFromStart=8.0974
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
Why is the BYE being sent so quickly?
This is an intermediate UAS proxy, and every now and
then it spits out an extra BYE like this. Shouldn't
this wait 500ms before doing a retry? The rest of the trace
is clean. I can forward the whole thing if there is any interest.
-g
--
Greg Fausak
greg(a)thursday.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
25 Feb
25 Feb
2:30 a.m.
On 02/23/06 23:50, Greg Fausak wrote:
Daniel,
I see now. You are using alarm() call?
I think it would be better for the first timeout to be more than a second.
We are seeing initial timeouts in the 30ms range...some of the
big boys don't like it. Can't I set the t1 timeout individually?
You cannot set it from config file. For the T1, the time out is set to
next timer event. To change the value, see the config.h file in the tm
module, there are the timer values.
Cheers,
Daniel
I'll try setting it
to 2 :-)
-g
On 2/23/06, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
Hello Greg,
the issue comes from the internal timer of openser, it has a fidelity of
one seconds, so for the first retransmission it might be under 500ms.
Does this issue cause troubles? We are looking to an alternative to
improve the timer in this respect, but no timeline at this moment.
Cheers,
Daniel
On 02/23/06 19:48, Greg Fausak wrote:
> I'm doing an interop test with a well known
> ITPS, they are kicking back these BYE retransmits, like:
>
> SIP MESSAGE 18 216.138.115.30:5061(www.testnode-3.com) ->
> 209.247.16.2:5060(deneps551.Denver1)
> UDP Frame 18 17/Feb/06 17:09:36.8142
> TimeFromPreviousSipFrame=0.0010 TimeFromStart=8.0692
> BYE sip:209.247.16.2:5060 SIP/2.0
> Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
> Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
> Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
> Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
> Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
> Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
> From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
> To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
> Call-ID: DEN05020060217230928060500(a)209.244.48.214
> CSeq: 101 BYE
> Max-Forwards: 67
> Record-Route: <sip:198.41.9.65:5060>
> Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
>
>
> SIP MESSAGE 19 216.138.115.30:5061(www.testnode-3.com) ->
> 209.247.16.2:5060(deneps551.Denver1)
> UDP Frame 19 17/Feb/06 17:09:36.8424
> TimeFromPreviousSipFrame=0.0282 TimeFromStart=8.0974
> BYE sip:209.247.16.2:5060 SIP/2.0
> Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
> Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
> Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
> Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
> Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
> Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
> From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
> To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
> Call-ID: DEN05020060217230928060500(a)209.244.48.214
> CSeq: 101 BYE
> Max-Forwards: 67
> Record-Route: <sip:198.41.9.65:5060>
> Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
>
>
> Why is the BYE being sent so quickly?
> This is an intermediate UAS proxy, and every now and
> then it spits out an extra BYE like this. Shouldn't
> this wait 500ms before doing a retry? The rest of the trace
> is clean. I can forward the whole thing if there is any interest.
>
> -g
>
> --
> Greg Fausak
> greg(a)thursday.com
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>
>
--
Greg Fausak
greg(a)thursday.com
2:49 a.m.
Hello again,
On 02/24/06 17:30, Daniel-Constantin Mierla wrote:
On 02/23/06 23:50, Greg Fausak wrote:
I overlooked it, actually you can tune it
from config file via tm module
parameters:
http://openser.org/docs/modules/1.0.x/tm.html#AEN148
Cheers,
Daniel
Daniel,
I see now. You are using alarm() call?
I think it would be better for the first timeout to be more than a
second.
We are seeing initial timeouts in the 30ms range...some of the
big boys don't like it. Can't I set the t1 timeout individually?
You
cannot set it from config file. For the T1, the time out is set to
next timer event. To change the value, see the config.h file in the
tm module, there are the timer values. 
24 Feb
24 Feb
7:16 p.m.
As far as I remember the timers were redesigned in ser recently, to have
finer granulation. maybe you can adopt this.
It really strange that ser sometimes send retransmission after 3 ms.
regards
klaus
Daniel-Constantin Mierla wrote:
Hello Greg,
the issue comes from the internal timer of openser, it has a fidelity of
one seconds, so for the first retransmission it might be under 500ms.
Does this issue cause troubles? We are looking to an alternative to
improve the timer in this respect, but no timeline at this moment.
Cheers,
Daniel
On 02/23/06 19:48, Greg Fausak wrote:
I'm doing an interop test with a well known
ITPS, they are kicking back these BYE retransmits, like:
SIP MESSAGE 18 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 18 17/Feb/06 17:09:36.8142
TimeFromPreviousSipFrame=0.0010 TimeFromStart=8.0692
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
SIP MESSAGE 19 216.138.115.30:5061(www.testnode-3.com) ->
209.247.16.2:5060(deneps551.Denver1)
UDP Frame 19 17/Feb/06 17:09:36.8424
TimeFromPreviousSipFrame=0.0282 TimeFromStart=8.0974
BYE sip:209.247.16.2:5060 SIP/2.0
Record-Route: <sip:216.138.115.30:5061;ftag=245-192.168.10.1;lr>
Record-Route: <sip:216.138.115.27;ftag=245-192.168.10.1;lr>
Via: SIP/2.0/UDP 216.138.115.30:5061;branch=z9hG4bK036d.a99621d6.0
Via: SIP/2.0/UDP 216.138.115.27;branch=z9hG4bK036d.1fe4ca41.0
Via: SIP/2.0/UDP 198.41.9.65:5060;branch=z9hG4bK245-192.168.10.1.256
Via: SIP/2.0/UDP 192.168.10.23:5060;branch=z9hG4bK1371-192.168.10.23.1374
From: <sip:+18663072489@216.138.115.30:5061>;tag=245-192.168.10.1
To: "Unknown" <sip:+17205626376@209.247.16.2>;tag=VPSF50603522629634
Call-ID: DEN05020060217230928060500(a)209.244.48.214
CSeq: 101 BYE
Max-Forwards: 67
Record-Route: <sip:198.41.9.65:5060>
Contact: "8663072489" <sip:+18663072489@198.41.9.65:1074>
Why is the BYE being sent so quickly?
This is an intermediate UAS proxy, and every now and
then it spits out an extra BYE like this. Shouldn't
this wait 500ms before doing a retry? The rest of the trace
is clean. I can forward the whole thing if there is any interest.
-g
--
Greg Fausak
greg(a)thursday.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6927
days inactive
6928
days old
5 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Greg Fausak -
Klaus Darilion