How to determine MO and MT call in SIP Networks
kiran kumar <[email protected]> Tue, 11 Oct 2011 23:29:55 +0530
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <CAGW1TF7PtHpO6DEgCpxb5kSUzWd4Pxc+PhFaAMvJh5gM7dp_tQ@mail.gmail.com> |
--===============8900105564441188134== Content-Type: multipart/alternative; boundary=0016e6ddff0bfa62fe04af09adce --0016e6ddff0bfa62fe04af09adce Content-Type: text/plain; charset=ISO-8859-1 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. --0016e6ddff0bfa62fe04af09adce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,<br><br>I am developing a SIPB2B which acts as a session controller.= <br>No registration mechanism is implemented in it. <br>It will directly re= ceives Invite from UAC and forwards it to UAS after successful billing auth= entication.<br> <br>Can any one help me, how could I distinguish between MO and MT calls (I= n pure SIP networks). <br>Is there any SIP header to determine the call typ= e.<br><br>Thanks,<br>Kiran.<br><div style=3D"visibility: hidden; left: -500= 0px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; mar= gin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-s= ize: 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup"= > </div> --0016e6ddff0bfa62fe04af09adce-- --===============8900105564441188134== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications. --===============8900105564441188134==--