Hi,
I'm trying to figure out what is the correct behaviour (in regards to
Loop Detection) in the following scenario:
We use DSLAM with VoIP capabilities which can manage 60 VoIP accounts
per card.
Let's assume the following configuration:
- two accounts A and B configured on the same card
There're bugs in loop detection of rfc3261,
Check draft-ietf-sip-fork-loop-fix-08, which will fix it eventually.
Regards,
-Rockson
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Bogdan-Andrei
Thanks - I will do so!
Regards,
Bogdan
Rockson Li (zhengyli) wrote:
There're bugs in loop detection of rfc3261,
Check draft-ietf-sip-fork-loop-fix-08, which will fix it eventually.
Regards,
-Rockson
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
Hi,
There're bugs in loop detection of rfc3261,
Check draft-ietf-sip-fork-loop-fix-08, which will fix it eventually.
The loop detection logic described in rfc3261 never detects a request
as looped when it is actually NOT. There is a potential scenario which
can occur during forking in which
Hi, I try to setup tests with sipp, openser and resiprocate.
resiprocate (192.168.160.23:6091) initiate the calls
sip routeur is 192.168.160.141:5060
uas is sipp 192.168.160.141:5061
sipp initiates a BYE which is routed correctly by openser but rejected
by resiprocate.
Request Uri, from and to
2009/1/23 Bogdan-Andrei Iancu bog...@voice-system.ro:
Hi,
actually the scenario does not imply any actual looping or spiralling.
Maybe the following chart will be more explicit:
X Proxy DSLM (A and B)
--- -INVITE A--
2009/1/23 Aurelien Grimaud gste...@yahoo.fr:
Hi, I try to setup tests with sipp, openser and resiprocate.
resiprocate (192.168.160.23:6091) initiate the calls
sip routeur is 192.168.160.141:5060
uas is sipp 192.168.160.141:5061
sipp initiates a BYE which is routed correctly by openser but
Hello,
No, the BYE's R-URI is ok (Callee side is releasing).
Probably it's the From and To header of the BYE that are incorrect.
Best regards,
Ben.
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On
BONNAERENS Ben a écrit :
Hello,
No, the BYE's R-URI is ok (Callee side is releasing).
Probably it's the From and To header of the BYE that are incorrect.
Best regards,
Ben.
Well, From and To header fields are exactly the same in all requests and
replies.
(ezxcept To for INVITE and
Hello,
That's exactly the point.They shouldn't be the same.
Please check scenario 3.1 of RFC3665.
Best regards,
Ben.
From: Aurelien Grimaud [mailto:gste...@yahoo.fr]
Sent: vrijdag 23 januari 2009 15:10
To: BONNAERENS Ben
Cc: Iñaki Baz Castillo;
Thank you, I missed this.
Working much better now that I changed sipp scenario.
It nows get From and To from ACK and replicate them in BYE as To and
From respectively.
Regards
Aurelien
BONNAERENS Ben a écrit :
Hello,
That's exactly the point.They shouldn't be the same.
Please check
That work is now available as RFC5393
RjS
On Jan 23, 2009, at 4:14 AM, Rockson Li (zhengyli) wrote:
There're bugs in loop detection of rfc3261,
Check draft-ietf-sip-fork-loop-fix-08, which will fix it eventually.
Regards,
-Rockson
-Original Message-
From:
On Fri, 2009-01-23 at 10:07 +0530, karthik karthik wrote:
305 has 3 contacts.
Proxy decided to recurse on first 2 contacts.
For some reasons Proxy decided not too recurse on the 3rd contact.
Meanwhile, If proxy received 4xx from 2nd contact, (and not all the
contacts are recursed)
305 will
Hi,
I have a few question regarding interpretation of RFC 3265. Paragraph
3.2.2 states that:
If the NOTIFY request fails (as defined above) due to a timeout
condition, and the subscription was installed using a soft-state
mechanism (such as SUBSCRIBE), the notifier SHOULD remove the
So for non-recoverable errors, it really does mean the subscription is
gone.
(Recoverable errors are things like digest challenges or complaints
about body of the NOTIFY).
Non-recoverable errors could be transport errors (ICMP) or SIP responses
(like a 480 from a proxy that can't get things
Thanks Inaki.
I am new to SIP and I may ask naive questions.
All I want, is to build a presence prototype soon. (presence client + presence
server)
So, it will be better for me, if there is any available open source presence
client and server in C/C++ or other languages
which can be readily
16 matches
Mail list logo
