>>> a cost which does not need to be incurred. ... Unless you want to make sure you interoperate in all situations, not just your controlled call center.
I would offer one could ALWAYS do a much more efficient protocol for a closed environment. We spend a lot of overhead to make sure all the corner cases work. This is one of those corner cases. On 10/18/07 7:18 PM, "Hadriel Kaplan" <[EMAIL PROTECTED]> wrote: > > >> -----Original Message----- >> From: Eric Burger [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 18, 2007 6:02 PM >> To: Hadriel Kaplan >> Cc: IETF SIP List >> Subject: Re: [Sip] Unsolicited NOTIFY/INFO versus Solicited State Update >> >> Ooooooh. That¹s right. Six messages. Instead of...??? Well? > > You said: "However, even for a 10,000 seat call center, we are talking about a > pretty trivial number of messages compared to the total interaction." > By "total interaction", I assumed you meant from a SIP signaling perspective. > Doubling the number of SIP messages is more than a "trivial number" compared > to the total number of SIP messages. Or at least, I wouldn't mind that kind > of "trivial" increase to my salary. ;) > > >> We are not talking about wireless networks here. Baseband networking sends >> the bits, whether they are being used or not. > > Absolutely. And we're not talking about IP routers or Ethernet switches > either. > I'm talking about SIP servers. You know, those things you say are ancient > concepts: stateful proxies, or app servers, or b2bua's, or PBXs/call-managers, > etc. I know not everyone thinks those things should exist. No one's forcing > them on you. But they do exist. And doubling the number of SIP messages and > state has an impact on them... a cost which does not need to be incurred. > > -hadriel > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
