Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion SIP B2BUA vs Proxy Server
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Generic Usenet Account  
View profile  
 More options Jun 17 2011, 6:41 pm
Newsgroups: comp.protocols.tcp-ip, comp.protocols.misc, comp.sources.d
From: Generic Usenet Account <use...@sta.samsung.com>
Date: Fri, 17 Jun 2011 15:41:18 -0700 (PDT)
Local: Fri, Jun 17 2011 6:41 pm
Subject: SIP B2BUA vs Proxy Server
Hello,

From an implementation perspective, what is the difference between a
SIP B2BUA and a Proxy Server (especially Stateful Proxy Server)?
According to http://www.b2bua.org, the difference between a SIP B2BUA
vs Proxy Server is as follows:

"Unlike a SIP proxy server, which only maintains transaction state,
the B2BUA maintains complete call state and participates in all call
requests. For this reason it can perform number of functions that are
not possible to implement using SIP proxy, such as for example
accurate call accounting, pre-paid rating and billing, fail over call
routing etc."

Does this mean that the B2BUA should have all the logic that normally
resides in a terminal device?  After all, it is two UAs back to back.
I don't see much description for B2BUA in RFC3261.

Is the above description correct?

Thanks,
Song


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.