Re: sendRecv and busy tone on physical termination in the sametime

Deepak Bissa <[email protected]>
Newsgroups gmane.ietf.megaco
Message-ID <31F873353B13F2419C80FD0833E118951147D312DE@GUREXMB01.ASIAN.AD.ARICENT.COM>
Hello,
In my view, MGC should set the mode to Inactive if it wants to play busy tone. MGC was not able to complete the requested session and applied busy tone. In such circumstances there is no need for keeping the resources allocated at MG for the session.

However, I would like to know the specific scenario where MGC is setting the mode to send/receive and applying busy tone in same packet.

For second part of the query, as per protocol H.248.1 (V3) section 7.2:
" The descriptors shall be processed in the order in which they appear".
So, the media descriptor containing mode as send/receive and signal descriptor for application of busy tone should be processed in order of their appearance in the command.

With regards,
Deepak Bissa

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Maxim Treskin
Sent: Wednesday, July 30, 2008 10:48 PM
To: [email protected]
Subject: [Megaco] sendRecv and busy tone on physical termination in the sametime

Hello

Is it normal, when MGC sends me signal cg/bt and termination mode
send/receive in the same packet?
Which behaviour must be realised on this termination: switch TDM port
of termination to RTP or signal to it busy?

Thank you
--
Maxim Treskin
_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus."
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.