Re: [Sip] Inquiry:SIP sending dialed digits in one-by-one digit format?

"Dale Worley" <dworley@avaya.com> Wed, 06 January 2010 18:51 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E2CD3A6936 for <sip@core3.amsl.com>; Wed, 6 Jan 2010 10:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n3CehE-wPoAq for <sip@core3.amsl.com>; Wed, 6 Jan 2010 10:51:15 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 1E9E23A6932 for <sip@ietf.org>; Wed, 6 Jan 2010 10:51:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,230,1262581200"; d="scan'208";a="170661379"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jan 2010 13:51:01 -0500
Received: from unknown (HELO zcars04f.nortel.com) ([47.129.242.57]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jan 2010 13:51:00 -0500
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o06Iod607432; Wed, 6 Jan 2010 18:50:39 GMT
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o06IobT26714; Wed, 6 Jan 2010 18:50:37 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Jan 2010 13:50:36 -0500
From: "Dale Worley" <dworley@avaya.com>
To: hadi motamedi <motamedi24@gmail.com>
In-Reply-To: <74aa57df1001052211s1658c619u6d594efc659de9be@mail.gmail.com>
References: <ea550427-7c74-4afe-b0e6-b6b8a97db582@u7g2000yqm.googlegroups.com> <74aa57df1001052211s1658c619u6d594efc659de9be@mail.gmail.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 06 Jan 2010 13:50:36 -0500
Message-Id: <1262803836.3744.23.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jan 2010 18:50:36.0591 (UTC) FILETIME=[224113F0:01CA8F01]
X-Mailman-Approved-At: Fri, 08 Jan 2010 11:52:16 -0800
Cc: sip@ietf.org
Subject: Re: [Sip] Inquiry:SIP sending dialed digits in one-by-one digit format?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2010 18:53:09 -0000

On Wed, 2010-01-06 at 06:11 +0000, hadi motamedi wrote:
> Can you please do me favor and let me know if it is technically
> feasible to send the sip dialed digits in one-by-one-digit format ? I
> mean if the subs dials say 6659983 we try to send it as 6,6,5,9,9,8,3
> but not as 6659983 in just one package with sip invite .

This is called "overlapped dialing", and there is a defined technique
for doing this.  The phone, when it receives the first digit, sends an
INVITE:

INVITE sip:6@domain SIP/2.0 -->

The proxy for the domain determines that additional digits are required,
and gives a 484 Address Incomplete response:

<-- SIP/2.0 484 Address Incomplete

When the user dials the second digit, the phone sends the accumulated
digits:

INVITE sip:66@domain SIP/2.0 -->

The proxy responds 484 again:

<-- SIP/2.0 484 Address Incomplete

This continues until the user enters a complete dial string.

However, this technique is not commonly used due to the high signaling
traffic it generates and the general difficulty having the proxy
determine whether or not the dial string is ended for all possible dial
strings.

A more common technique is to program the UA with a "dial pattern",
which is a regular expression that describes all valid dial strings.
E.g., three-digit extensions could be described "xxx", while "9 followed
by 7 digits" could be described "9xxxxxxx".  Also, the dial pattern
language usually allows a way of specifying variable-length strings via
"a series of digits terminated by a time-out":  "9xT".  This method
places the entire burden on the UA, but allows a mixture of fixed- and
variable-length strings in the dial plan.  Of course, the details vary
from one make of UA to another.

Dale