[SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..

Thu May 15 17:48:23 EDT 2008

That's a very good question.  And I may not be 100% up to speed on IP trunking, but I have a service to deliver soon, and I'm looking for working solutions.

What we're asking service providers to do, is to possibly be the "Centrex-like" solution for the SOHOs, providing a pool of registerable numbers that would route inbound to a local SIP trunk at the SOHO location, but alternate route those same numbers to an enterprise route, if the primary location is unavailable.  Is that what you would consider a line side or trunk side call if it's transferred by the carrier?  If the carrier is providing the MPLS infrastructure, over which a SIP-administered phone is riding from the small office, and they administer those on behalf of the enterprise, would that be considered line side or trunk side to the SOHO?   They need to be able to alternate route or transfer in either scenario regardless of the definition of the point of demarcation.

If we ask SPs to provide cellular integration with our corporate network, through SIP trunks, then they are providing the numbers, and we are only providing transport integration.  That's a trunk imho.

In these scenarios, transfer of calls will be quite common.  We need to have a good mechanism for determining who will "handle" the RT audio or video transfer, and mechanisms for determining who is the session handler.  Determining who is the session handler will make it easier to determine how the billing is handled, which is a large point of contention on cross-environment VoIP today, regardless of who is providing the number.

Does this provide some clarification?  If there's something out there that already defines this, please let me know.

Sandra.Cirlincione @boeing.com
SSG - IT, Enterprise Voice Engineering, VoIP/Convergence
Desk 206.766.5888    (One number reach)
Home Office 425.373.8293
MOC Pilot  425.865.3214
Cell 425.417.3138
Wishing you happiness, hope, or health, take what you need.

-----Original Message-----
From: Uzelac, Adam [mailto:Adam.Uzelac at globalcrossing.com]
Sent: Thursday, May 15, 2008 1:54 PM
To: Cirlincione, Sandra; Hadriel Kaplan; Jamie Palmer; Richard Shockey; SIP Forum TechWG
Subject: RE: [SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..

Sandra - I understand what you are saying, but would like to ask the
following for clarification.  What are the UA's registering to from the
small branch offices/teleworking locations?  If the answer is the IP-PBX
at the headquarters, and this is being done via an IP-VPN-like (or other
remote access mechanism) connection, then the branch office is more like
an extension to the Enterprise SIP domain.  The "SIP Trunk" from
headquarters to the SSP is the one that would handle the access to the
PSTN.

BUT.... If you are thinking of the scenario that the branch
offices/teleworkers are registering to something WITHIN the SSP's
administrative domain, then I agree 100% with you.  And with that
agreement comes my request that the scope of the 1.0 (or 1.1)
specification be amended.

-AU

> -----Original Message-----
> From: Cirlincione, Sandra [mailto:sandra.cirlincione at boeing.com]
> Sent: Thursday, May 15, 2008 4:44 PM
> To: Hadriel Kaplan; Uzelac, Adam; Jamie Palmer; Richard
> Shockey; SIP Forum TechWG
> Subject: RE: [SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..
>
> I support a large enterprise, with the perspective that it
> could be both.
>
> If we might entertain that the large corporation has major
> locations, with trunk side integrations for the various
> campuses that house thousands of users connected to IP-PBXs
> and remotes internally, but also has line side remotes for
> teleworkers and small branch offices.  In this environment,
> the service provider may have to provision both to the same
> enterprise.
>
> While the major sites have the volume for the trunk
> deployments, the smaller branches still have the same
> requirement for the carrier integration, redundancy and
> failover to the major corporation for alternate routing
> during outages.  Typically these configurations would have
> the same security, potentially the same codec and endpoint
> routing serviceability requirements, including not only
> voice, but video and fax as well.
>
>
> Sandra.Cirlincione @boeing.com
> SSG - IT, Enterprise Voice Engineering, VoIP/Convergence
> Desk 206.766.5888    (One number reach)
> Home Office 425.373.8293
> MOC Pilot  425.865.3214
> Cell 425.417.3138
> Wishing you happiness, hope, or health, take what you need.
>
>
> -----Original Message-----
> From: techwg-bounces at sipforum.org
> [mailto:techwg-bounces at sipforum.org] On Behalf Of Hadriel Kaplan
> Sent: Thursday, May 15, 2008 1:18 PM
> To: Uzelac, Adam; Jamie Palmer; Richard Shockey; SIP Forum TechWG
> Subject: Re: [SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..
>
> Hey Adam,
>
> > -----Original Message-----
> > From: techwg-bounces at sipforum.org
> [mailto:techwg-bounces at sipforum.org]
> > On Behalf Of Uzelac, Adam
> > >
> > > 1) Section 11 (Enterprise Identities):  I would like to see this
> > > section revised to cover the registration process.
> >
> > I disagree.  In my view, the relationship between the
> Enterprise with
> > a IP-PBX, and a SIP Service Provider (SSP) is  a "trunking"
> relationship.
> > I view a SIP Registration process as "line" side.  This is
> consistent
> > with the text in the introduction of the document: "this document
> > defines the protocol support, implementation rules, and features
> > required for a predictable interoperable scenario between
> SIP-enabled
> > IP PBXs and SIP-enabled Service Providers."
>
> I think you're actually both right. :)  There are providers
> which treat their Enterprise customers as "line side", and
> many that treat it as "trunk side".  The difference I've seen
> so far is around the size of the Enterprises being connected
> - for medium/large Enterprises, it's a defined trunk; for
> SMB's the provider treats them as a line side to some degree,
> specifically with a Registration process.  The needs of those
> two markets are different, for both provider and enterprise, methinks.
>
> -hadriel
>
> _______________________________________________
> techwg mailing list
> Send mail to: techwg at sipforum.org
> Unsubscribe or edit options at:
> http://sipforum.org/mailman/listinfo/techwg
>