[SIPForum-techwg] SF SIP Phone Spec -- Proposed structure
Karthikeyan.Sankaran at infineon.com
Karthikeyan.Sankaran at infineon.com
Mon Jun 11 23:56:07 EDT 2007
HI Peter,
Yes, that is what I meant from call toggle, ability to switch between
calls.
regards
Karthik
________________________________
From: peter_blatherwick at mitel.com [mailto:peter_blatherwick at mitel.com]
Sent: Tuesday, June 12, 2007 2:17 AM
To: Sankaran Karthikeyan (IFIN SW WL)
Cc: techwg at sipforum.org
Subject: Re: [SIPForum-techwg] SF SIP Phone Spec -- Proposed structure
Thanks Karthik,
Agree, we should add these suggestions to the pile. Some of your
suggestions are already in the update Marek sent around a little earlier
today, e.g. call waiting, RFC2833 in-band tones (now replaced by
4733-4734 actually).
BTW, by "call toggle" do you mean the ability to switch between multiple
ongoing calls (eg. calls on hold), or something else?
Cheers
Peter Blatherwick
<Karthikeyan.Sankaran at infineon.com>
Sent by: techwg-bounces at sipforum.org
08.06.07 01:08
To: <techwg at sipforum.org>
cc:
Subject: Re: [SIPForum-techwg] SF SIP Phone Spec --
Proposed structure
HI Mr Peter,
Following is my quick list of features for consideration:
Telephony features:
- Call forward on DND. This may be an internal phone feature.
- Call toggle. This may be an internal phone feature
- Call waiting. e.g. Call Waiting) are already listed in the update
Allows user to make/receive call when one already
ongoing.
- Auto answer. This may be an internal phone feature.
Mandatory feature:
- RTP. RFC 3550
Recommended feature:
- SIP Session timer. RFC 4028
- DTMF Handling. RFC 2833
- TR-104 support for configuration
Advanced feature:
- VAD. voice activated dialing. Phone feature
Regards
Karthik
-----Original Message-----
From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org]
On Behalf Of techwg-request at sipforum.org
Sent: Wednesday, May 30, 2007 7:19 PM
To: techwg at sipforum.org
Subject: techwg Digest, Vol 19, Issue 28
Send techwg mailing list submissions to
techwg at sipforum.org
To subscribe or unsubscribe via the World Wide Web, visit
http://sipforum.org/mailman/listinfo/techwg
or, via email, send a message with subject or body 'help' to
techwg-request at sipforum.org
You can reach the person managing the list at
techwg-owner at sipforum.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of techwg digest..."
Today's Topics:
1. Re: SF SIP Phone Spec -- Proposed structure and
content for
Telephony section (trial balloon) (larry schessel)
2. SF SIP Phone Spec -- Proposed structure and content for
Telephony section (trial balloon) (peter_blatherwick at mitel.com)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 May 2007 12:34:06 -0400
From: "larry schessel" <lschesse at gmail.com>
Subject: Re: [SIPForum-techwg] SF SIP Phone Spec -- Proposed structure
and content for Telephony section (trial
balloon)
To: "peter_blatherwick at mitel.com" <peter_blatherwick at mitel.com>
Cc: SIP Forum Tech WG <techwg at sipforum.org>
Message-ID:
<14010c9d0705290934p58e2ba9et931aa5b2048b5134 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Just a few more features to consider:
- Auto Callback features
- Do Not Disturb (maybe only internal phone feature)
- MWI
We should finalize the list today and then agree the next level we need
to define each feature.
Larry
On 5/28/07, peter_blatherwick at mitel.com <peter_blatherwick at mitel.com>
wrote:
>
>
> Hi John,
>
> The doc I sent around was intended only to show proposed structure and
> flesh out some possible set of Telephony functions. It was based
> simply on a striped down version of the previous draft (unnecessary
> sections removed is all). So all you're seeing is remnants of
> whatever was written down before.
>
> But both of your comments are valid, and I personally agree with the
both.
> We at least need to discuss whether both UDP and TCP are MUST or not.
>
> > o It is FAR from complete.
> Seems I have lived down to the expectation ;-) Perhaps I should have
> added "or even accurate"
>
> -- Peter
>
>
>
>
> *"Elwell, John" <john.elwell at siemens.com>*
>
> 27.05.07 06:15
>
> To: peter_blatherwick at mitel.com, SIP Forum Tech WG <
> techwg at sipforum.org>
> cc:
> Subject: RE: [SIPForum-techwg] SF SIP Phone Spec --
> Proposed structure and content for Telephony section (trial balloon)
>
>
>
>
> Peter,
>
> A couple of comments.
>
> 1. Why RFC 2327? This has been obsoleted by RFC 4566.
>
> 2. Why mandate support for UDP? There has been much discussion on the
> SIP list in recent months about this (in the context of sip-outbound),
> and although there is certainly not a consensus to deprecate UDP yet,
> difficulties with large message sizes means that you effectively have
> to support TCP, at least for large messages, unless you know your
> implementation will be deployed only in environments where large
> messages simply cannot occur.
>
> John
>
> ------------------------------
> *From:* techwg-bounces at sipforum.org
> [mailto:techwg-bounces at sipforum.org] *On Behalf Of
> *peter_blatherwick at mitel.com*
> Sent:* 25 May 2007 19:08*
> To:* SIP Forum Tech WG*
> Subject:* [SIPForum-techwg] SF SIP Phone Spec -- Proposed structure
> and content for Telephony section (trial balloon)
>
>
> OK, I'll try this again, this time with .doc file only. The email
> list is blocking due to size. If anyone wants .html format, just let
me know...
> -- Peter Blatherwick
>
>
> ----- Forwarded by Peter Blatherwick/Kan/Mitel on 25.05.07 14:06 -----
*Peter
> Blatherwick*
>
> 25.05.07 14:02
>
> To: "SIP Forum Tech WG" <techwg at sipforum.org>
> cc: "Larry Schessel" <lschesse at gmail.com>
> Subject: SF SIP Phone Spec -- Proposed structure and
content
> for Telephony section (trial balloon)
>
>
>
>
> Hi all,
>
> As actioned last week, here is an initial stab at a general structure
> which might be usable for the feature set sections of the SF SIP Phone
> Interop spec. See attached (both .doc and .html).
>
> Some notes:
>
> o This is for discussion purposes only at this point, so we have
> something concrete to complain about.
>
> o Section 0 proposes a general structure.
>
> o Section 6.4 tries to put the proposed structure to the test, to see
> how it would flow. Only a few features are spelled out so far, in the
> interest of not doing too much work before we agree on structure.
>
> o I have also tried to flesh out the feature set for Telephony in
section
> 6.4, grouping specific features into 4 different feature subsets. I
> borrowed shamelessly from the TIA spec Joanne sent pointers for last
week
> (TIA-811-A). I'm certain we will haggle over this for some time, but
hey,
> its a start !
>
> o It is FAR from complete. Hopefully enough bare bones are there to
> at least see if the structure can fly or not.
>
> Comments in advance of next week's conf call would be appreciated.
(My
> flame proof suit is on ! ;-)
>
> Cheers,
> Peter Blatherwick
>
>
> <SF_SIP_Phone_Interop - Proposal for Telephony - PB 00.doc>
>
>
> _______________________________________________
> techwg mailing list
> Send mail to: techwg at sipforum.org
> Unsubscribe or edit options at:
> http://sipforum.org/mailman/listinfo/techwg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://sipforum.org/pipermail/techwg/attachments/20070529/182a6992/attac
hment-0001.html
------------------------------
Message: 2
Date: Fri, 25 May 2007 14:02:42 -0400
From: peter_blatherwick at mitel.com
Subject: [SIPForum-techwg] SF SIP Phone Spec -- Proposed structure and
content for Telephony section (trial balloon)
To: "SIP Forum Tech WG" <techwg at sipforum.org>
Message-ID:
<OFF58BDEB8.8572F867-ON852572E6.00617D50-852572E6.00631F45 at mitel.com>
Content-Type: text/plain; charset="us-ascii"
Hi all,
As actioned last week, here is an initial stab at a general structure
which might be usable for the feature set sections of the SF SIP Phone
Interop spec. See attached (both .doc and .html).
Some notes:
o This is for discussion purposes only at this point, so we have
something concrete to complain about.
o Section 0 proposes a general structure.
o Section 6.4 tries to put the proposed structure to the test, to see
how it would flow. Only a few features are spelled out so far, in the
interest of not doing too much work before we agree on structure.
o I have also tried to flesh out the feature set for Telephony in
section
6.4, grouping specific features into 4 different feature subsets. I
borrowed shamelessly from the TIA spec Joanne sent pointers for last
week
(TIA-811-A). I'm certain we will haggle over this for some time, but
hey, its a start !
o It is FAR from complete. Hopefully enough bare bones are there to at
least see if the structure can fly or not.
Comments in advance of next week's conf call would be appreciated. (My
flame proof suit is on ! ;-)
Cheers,
Peter Blatherwick
<SF_SIP_Phone_Interop - Proposal for Telephony - PB 00.doc>
<SF_SIP_Phone_Interop - Proposal for Telephony - PB 00.htm>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://sipforum.org/pipermail/techwg/attachments/20070525/a15e5355/attac
hment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SF_SIP_Phone_Interop - Proposal for Telephony - PB
00.doc
Type: application/octet-stream
Size: 88064 bytes
Desc: not available
Url :
http://sipforum.org/pipermail/techwg/attachments/20070525/a15e5355/attac
hment.obj
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://sipforum.org/pipermail/techwg/attachments/20070525/a15e5355/attac
hment.htm
------------------------------
_______________________________________________
techwg mailing list
Send mail to: techwg at sipforum.org
Unsubscribe or edit options at:
http://sipforum.org/mailman/listinfo/techwg
Unsubscribe or edit options at:
http://sipforum.org/mailman/listinfo/techwg
End of techwg Digest, Vol 19, Issue 28
**************************************
_______________________________________________
techwg mailing list
Send mail to: techwg at sipforum.org
Unsubscribe or edit options at:
http://sipforum.org/mailman/listinfo/techwg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20070612/7b15d335/attachment.html
More information about the techwg
mailing list