2011/1/20 Kondaveeti Seshagiri :
> If proxy not retransmit non-2XX final responses to a TCP UAC, then
> What is difference between transport over UDP and TCP?
non 2XX responses are hop by hop, so if a SIP UAS or proxy replies a
non-2XX via TCP it doesn't need to send retransmissions as it
*already
2011/1/20 prashanth.me :
> As per the RFC 3261 in section 18.1.2, On receiving a Response must
> check the Sent-By field of VIA header to that of configured in Request.
> Are the below sent-by params of VIA header in Request and Response are
> same? Should UA discard the response?
>
> Request conta
Hi,
As per the RFC 3261 in section 18.1.2, On receiving a Response must
check the Sent-By field of VIA header to that of configured in Request.
Are the below sent-by params of VIA header in Request and Response are
same? Should UA discard the response?
Request contains sent-by IP and port:
Via:
No not in this case. The B side of the scenario is a SIPp test script so I
pretty much decides myself what to do there. The problem is that SIPp will
complain and exit the scenario when signaling comes on the second TCP connection
// Andreas
-Original Message-
From: santosh.kalsang...@w
I have doubt in this case.
If proxy not retransmit non-2XX final responses to a TCP UAC, then
What is difference between transport over UDP and TCP?
I think TCP i.e. at Transport layer sends data reliably (Retransmits if not
received Acknowledgement for TCP packet) irrespective of Application l
Hi,
As per O/A model rfc 3264 re-invite offer with SDP containing connection IP
0.0.0.0 is not recommended . Since UA neither send any RTP/RTCP as the
destination media address is not known nor receive any RTP/RTCP from 0.0.0.0.
we are facing interop issue with B2BUA when a re-Invite off
On 1/19/2011 4:13 AM, Sunil wrote:
> Hi All,
>
> Please clarify how to handle the below requirement of rfc 3261in case of
> 3 scenarios: The UAS MUST ensure that the session description overlaps
> with its previous session description in media formats, transports, or
> other parameters that requi
5th Conference on Principles, Systems and
Applications of IP Telecommunications
(IPTComm 2011)
http://www.iptcomm.org
August 1-2, 2011
Illinois Institute of Technology
Hi Andreas,
Is it 481 (call leg/transaction does not exist) response for BYE? I happen to
see same behavior but in different scenario.
Thanks,
Santosh
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Beha
Hi,
I've just recently started to look at a scenario when SIP is sent over TCP (not
UDP as I'm used to have). I see a behavior that I'm not really sure it correct:
It's a very basic SIP call UAA -> UAB
1. UAA sends INVITE to UAB
2. UAB answers with 180 and 200 OK
3. UAA send
Hi All,
Please clarify how to handle the below requirement of rfc 3261in case of
3 scenarios: The UAS MUST ensure that the session description overlaps
with its previous session description in media formats, transports, or
other parameters that require support from the peer.
1. User A and User
Hi Albert
In general,
- responses to requests (received on TCP) should be sent to source port.
- responses to requests (received on UDP) should be sent to port
present in Via.
However there are number of parameters those can affect your destination
transport params such as maddr
12 matches
Mail list logo
