Discussion:
[Sip-implementors] TCP/NAT handling in SIP
VARUN BHATIA
2014-04-29 10:52:09 UTC
Permalink
Hi,

If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).

1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?

Any inputs are appreciated.
--
Regards,
Varun Bhatia
Brett Tate
2014-04-29 11:05:13 UTC
Permalink
RFC 5626 will likely be helpful.
-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-
implementors-bounces at lists.cs.columbia.edu] On Behalf Of VARUN BHATIA
Sent: Tuesday, April 29, 2014 6:52 AM
To: sip-implementors
Subject: [Sip-implementors] TCP/NAT handling in SIP
Hi,
If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).
1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?
Any inputs are appreciated.
--
Regards,
Varun Bhatia
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.
VARUN BHATIA
2014-04-29 11:55:23 UTC
Permalink
Thanks Brett, is there any specific standard which indicates that INVITE
dialog will be using same connection of REGISTER ?

Thanks,
Varun
Post by Brett Tate
RFC 5626 will likely be helpful.
-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-
implementors-bounces at lists.cs.columbia.edu] On Behalf Of VARUN BHATIA
Sent: Tuesday, April 29, 2014 6:52 AM
To: sip-implementors
Subject: [Sip-implementors] TCP/NAT handling in SIP
Hi,
If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).
1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?
Any inputs are appreciated.
--
Regards,
Varun Bhatia
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.
--
Regards,
Varun Bhatia
Paul Kyzivat
2014-04-29 12:41:03 UTC
Permalink
Post by VARUN BHATIA
Thanks Brett, is there any specific standard which indicates that INVITE
dialog will be using same connection of REGISTER ?
RFC 5626 is the only one
Post by VARUN BHATIA
Thanks,
Varun
Post by Brett Tate
RFC 5626 will likely be helpful.
-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-
implementors-bounces at lists.cs.columbia.edu] On Behalf Of VARUN BHATIA
Sent: Tuesday, April 29, 2014 6:52 AM
To: sip-implementors
Subject: [Sip-implementors] TCP/NAT handling in SIP
Hi,
If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).
1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?
Any inputs are appreciated.
--
Regards,
Varun Bhatia
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.
ankur bansal
2014-04-29 15:35:33 UTC
Permalink
Hi Varun ,
I dont think sip protocol will have any issue with this .Means you can use
one TCP socket T1 for Register and another T2 for INVITE.
But if you talk about IMS and specifically IPSec feature then it may impact
.

UE1--------------------------P1
--------Register(T1)--->
IPSEC SA created on this socket T1
------INVITE(T1)--->
Call established then Tcp connection breaks,need to send register again on
new socket .
------Register(T2)----->
new IPSEC SA will be created for T2
----Re-invite hold(T1)---------->
<---500 --------------(as re-invite came from old client port so IPSec will
have issue )

So here after TCP connection breaks ,call should be dropped .All IMS
communcation should be in same connection as of Register.
You may get some reference in 3gpp spec 33.203 .

Thanks & regards
Ankur Bansal
Post by Paul Kyzivat
Post by VARUN BHATIA
Thanks Brett, is there any specific standard which indicates that INVITE
dialog will be using same connection of REGISTER ?
RFC 5626 is the only one
Thanks,
Post by VARUN BHATIA
Varun
RFC 5626 will likely be helpful.
-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-
implementors-bounces at lists.cs.columbia.edu] On Behalf Of VARUN BHATIA
Sent: Tuesday, April 29, 2014 6:52 AM
To: sip-implementors
Subject: [Sip-implementors] TCP/NAT handling in SIP
Hi,
If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).
1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?
Any inputs are appreciated.
--
Regards,
Varun Bhatia
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Varun Bhatia
2014-04-29 16:20:54 UTC
Permalink
Thanks Ankur, not sure if it is implemented in such manner then we should not honor new connection with INVITE?

Thanks,
Varun Bhatia
Post by ankur bansal
Hi Varun ,
I dont think sip protocol will have any issue with this .Means you can use
one TCP socket T1 for Register and another T2 for INVITE.
But if you talk about IMS and specifically IPSec feature then it may impact
.
UE1--------------------------P1
--------Register(T1)--->
IPSEC SA created on this socket T1
------INVITE(T1)--->
Call established then Tcp connection breaks,need to send register again on
new socket .
------Register(T2)----->
new IPSEC SA will be created for T2
----Re-invite hold(T1)---------->
<---500 --------------(as re-invite came from old client port so IPSec will
have issue )
So here after TCP connection breaks ,call should be dropped .All IMS
communcation should be in same connection as of Register.
You may get some reference in 3gpp spec 33.203 .
Thanks & regards
Ankur Bansal
Post by Paul Kyzivat
Post by VARUN BHATIA
Thanks Brett, is there any specific standard which indicates that INVITE
dialog will be using same connection of REGISTER ?
RFC 5626 is the only one
Thanks,
Post by VARUN BHATIA
Varun
RFC 5626 will likely be helpful.
-----Original Message-----
From: sip-implementors-bounces at lists.cs.columbia.edu [mailto:sip-
implementors-bounces at lists.cs.columbia.edu] On Behalf Of VARUN BHATIA
Sent: Tuesday, April 29, 2014 6:52 AM
To: sip-implementors
Subject: [Sip-implementors] TCP/NAT handling in SIP
Hi,
If the UA is behind NAT registers on TCP and after that it initiates a call
on same connection (may be another connection ?) after some time connection
break now as soon as UA detect that the connection is closed it initiates a
new REGISTER using new connection (It is not changing contact as it is
listening on default port).
1. Should UA send a re-invite/update for modifying the connection status
within a call ?
2. If No, then whether it is recommended in any of standard that we should
use the same connection for sending any request ?
3. Is there any RFC which mention the connection handling between REGISTER
request and INVITE request ?
Any inputs are appreciated.
--
Regards,
Varun Bhatia
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this email in error,
please notify BroadSoft, Inc. immediately by replying to this message, and
destroy all copies of this message, along with any attachment, prior to
reading, distributing or copying it.
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors at lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Loading...