IETF Logo Mail Archive

Re: [SIP] Some idea on Stateful SIP Proxy for Card Service

<ferreiro_j@tsm.es> Wed, 17 January 2001 11:34 UTC

Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA15540 for <sip-archive@odin.ietf.org>; Wed, 17 Jan 2001 06:34:54 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 06A174439E; Wed, 17 Jan 2001 05:35:04 -0500 (EST)
Delivered-To: sip@lists.bell-labs.com
Received: from aurora.tsm.es (unknown [194.224.100.20]) by lists.bell-labs.com (Postfix) with ESMTP id 37F9244391 for <SIP@lists.bell-labs.com>; Wed, 17 Jan 2001 05:34:22 -0500 (EST)
Received: by aurora.tsm.es; (8.8.8/1.3/10May95) id MAA31226; Wed, 17 Jan 2001 12:34:21 +0100 (MET)
From: ferreiro_j@tsm.es
Subject: Re: [SIP] Some idea on Stateful SIP Proxy for Card Service
To: james jack <sipjames@yahoo.com>
Cc: SIP@lists.bell-labs.com
Message-ID: <OFF9C700BD.2209B432-ONC12569D7.003E9118@tsm.es>
X-MIMETrack: Serialize by Router on abantos/TSM( Versión 5.0.5 |Octubre 21, 2000) at 17/01/2001 12:31:51 PM
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-BeenThere: sip@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:sip-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:sip@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/sip/
Date: Wed, 17 Jan 2001 12:31:49 +0100


You can check Third Party Call Control in SIP
(draft-rosenberg-sip-3pcc-01.txt) and, since it seems that you want to base
the charging on SIP message flows,  SIP session timer
(draft-ietf-sip-session-timer-04.txt)) in order to avoid neverending
charging when there is any problem when delivering BYE message.

Javier



>Dear All:
>   My question is on card serice, how to realize
> the traditional card service with SIP. one difficulty
> is that if the money in the card is over, how to
> control the terminal to break the connection.
>   For example, User B use the Terminal to dial
> terminal C through Proxy P, the charging is
>controlled by the application layer in proxy P--which
>can contact the database, then if the money in the
>card is over, how to control to break the connection?
>   In my opinion, the application layer of Proxy P
> can send a instruction, then the proxy send BYE to
>both sides (B and C), then the connection can be
>broken.
>  But the proxy will never generate BYE request
>according to RFC2543?  then how to solve such problem?
>  Any suggestions and ideas are welcome!
>  I am looking forwards to getting your reply as
> soon as possible!
>     Best Regards!
>                           Yours: james


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/

_______________________________________________
This list is for continuing development of the SIP protocol.
The sip-implementer's list is the place to discuss implementation,
and to receive advice on understanding existing sip.
To subscribe to it, send mail to majordomo@cs.columbia.edu with
"subscribe sip-implementors" in the body.




_______________________________________________
This list is for continuing development of the SIP protocol.
The sip-implementer's list is the place to discuss implementation,
and to receive advice on understanding existing sip.
To subscribe to it, send mail to majordomo@cs.columbia.edu with
"subscribe sip-implementors" in the body.

v2.23.0 | Report a Bug | By Email