[SIPForum-techwg] TCP vs. UDP (SP adoption of TCP?)

[Peter Dunkley]

That would depend on whether you consider ISDN, and the like, to be SIP related or not :-)

On a more serious note there is a requirement for tunnelling UK-ISUP within SIP messages.  Also, UK-ISUP has recently been extended to allow BT-NUP messages to be tunnelled within - specifically so that BT-NUP can be passed across a SIP network for legacy interworking.  This would result in SIP messages that can contain UK-ISUP messages, that can contain BT-NUP messages, which may contain DPNSS messages...

What you jokingly mentioned below is absolutely horrible - but (within a national context) not as unlikely as it may seem!

I have also heard of some interest in directly tunnelling DPNSS within SIP as well.

However, I would be the first to admit that BT-NUP and so on have no place in a SIPconnect recommendation.

Peter

-----Original Message-----
From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org]On
Behalf Of Eric Burger
Sent: 22 May 2008 10:17
To: techwg at sipforum.org
Subject: Re: [SIPForum-techwg] TCP vs. UDP (SP adoption of TCP?)


I would offer this philosophy would lead us to standardize SIPconnect  
1.1 to use ISDN, possibly choosing Q.921, Q.sig, or BT-NUP :-)

On May 21, 2008, at 10:24 AM, Peter Dunkley wrote:

> In my opinion any recommendation needs to take into account not just  
> best practice, but actual practice.  Vilifying, or making life  
> difficult, for those who have pragmatically chosen something  
> different, and invested time and money in making it work, is not  
> going to contribute to the success of any recommendation.

_______________________________________________
techwg mailing list
Send mail to: techwg at sipforum.org
Unsubscribe or edit options at:  http://sipforum.org/mailman/listinfo/techwg


NOTICE & DISCLAIMER 
This email including attachments (this "Document") is confidential and may contain legally privileged information.  If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents.  We cannot accept liability for any breaches of confidence arising through use of this Document.

The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement.  The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk.

Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis.  We will not accept responsibility for any commitments made by our employees outside the scope of our business.