[Sip] How to determine MO and MT call in SIP Networks

kiran kumar <g.kiranreddy4u@gmail.com> Tue, 11 October 2011 18:00 UTC

Return-Path: <g.kiranreddy4u@gmail.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECBAA21F8F7A; Tue, 11 Oct 2011 11:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuXllGXPXMpT; Tue, 11 Oct 2011 11:00:16 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2318F21F8F36; Tue, 11 Oct 2011 11:00:15 -0700 (PDT)
Received: by wwf22 with SMTP id 22so7501044wwf.13 for <multiple recipients>; Tue, 11 Oct 2011 11:00:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=w58I4sMEumQ59su+wSGOOiTFheMatJa4zs/wW817ODw=; b=CU00XcmMQkp7Jg1rEm9hNedAd5q0+VRAM3/4rHVlD5nIeZeQ2TP5zlHj/4wcEEKSZs rC6VjUBxgvd1EaJLwfBt2BoHRdnfubKNnPPZ6ofC5abxwTPnmSY8oM+OuYuhbTJZfgsu J3vgaw+P93cb2NB1zpV9pugimmOzFDOlYhv4Y=
Received: by 10.216.135.34 with SMTP id t34mr1176675wei.62.1318356015276; Tue, 11 Oct 2011 11:00:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.27.67 with HTTP; Tue, 11 Oct 2011 10:59:55 -0700 (PDT)
From: kiran kumar <g.kiranreddy4u@gmail.com>
Date: Tue, 11 Oct 2011 23:29:55 +0530
Message-ID: <CAGW1TF7PtHpO6DEgCpxb5kSUzWd4Pxc+PhFaAMvJh5gM7dp_tQ@mail.gmail.com>
To: sip-request@ietf.org, sip@ietf.org
Content-Type: multipart/alternative; boundary=0016e6ddff0bfa62fe04af09adce
Subject: [Sip] How to determine MO and MT call in SIP Networks
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 11 Oct 2011 18:00:17 -0000

Hi all,

I am developing a SIPB2B which acts as a session controller.
No registration mechanism is implemented in it.
It will directly receives Invite from UAC and forwards it to UAS after
successful billing authentication.

Can any one help me, how could I distinguish between MO and MT calls (In
pure SIP networks).
Is there any SIP header to determine the call type.

Thanks,
Kiran.