headers
B Venkat S.R Swamy | 2 Nov 2005 12:12

Fw: RequestID in EventsDescriptor





Hi

As mentioned in the protocol the behaviour in case RequestId is set to zero
is for further study and there has been lot of discussions on the mailing
list earlier on the same topic,
the links for some of which are mentioned below:


http://www1.ietf.org/mail-archive/web/megaco/current/msg05581.html


http://www.ietf.org/mail-archive/web/megaco/current/msg04845.html


If we summarize these discussions than one thing is quite evident that this
feature can be quite useful for certain scenarios involving big gateways or
for CAS scenario.
Also the way events are pre-provisioned, the requestID corresponding to
these events can be pre-provisioned and MGC behaviour on receiving
unsolicited event notification is known and agreeable to both the parties.
MGC can also be made aware of the armed events and corresponding requestID
by Auditing the MG.

Thus would request the ITU Megaco group to put some clarification on this
issue in protocol specification.

regards
B Venkat S.R Swamy
(Continue reading)

Permalink | Reply | 0 comments |
headers
B Venkat S.R Swamy | 2 Nov 2005 12:42

Re: Socket set-up.


Hi John

The exact behaviour in most cases is an implementation issue and depends on
factors such as network scenario(Trunking, residential, interworking etc),
mode of the termination at the time of ADD, resource policy implemented. So
for example  you have Mode of termination in Media Descriptor in ADD
command is set to "ReceiveOnly" or "SendReceive" then its likely that MG
will  open the RTP/ATM port for receiving the media(say for receiving the
RingBack tone) from peer node at the time of ADD itself.

regards
B Venkat S.R Swamy
Senior Technical Leader
Flextronics Software Systems
Phone:  +91-124- 5176333 extn 5113
Fax: +91-124-2455345
web: www.flextronicssoftware.com

                                                                           
             "Wainwright,                                                  
             John"                                                         
             <john.wainwright <at>                                           To 
             siemens.com>              megaco <at> ietf.org                     
             Sent by:                                                   cc 
             megaco-bounces <at> ie                                             
             tf.org                                                Subject 
                                       [Megaco] Socket set-up.             

             10/31/2005 09:28
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lee Kyoung-tae | 3 Nov 2005 11:42

TrFO IP-IP call flow for IMS MGW

Hi All.

I am making TrFO IP-IP call flow for IMS MGW.

I have some question.

- Are there packages for TrFO for IMS MGW?
- How about sdp attributes?
- where can I find TrFO IP-IP call flow for IMS MGW?
- I tried to make Add message for TrFO IP-IP call as following.
   What do you think about this message?

MEGACO/1 [172.21.0.100]:2944
Transaction = 1000 {
Context = $ {
  Add = RTP2/$ {
    Media {
      LocalControl { Mode = SendReceive },
      Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      Remote {
v=0
c=IN IP4 172.30.0.100
m=audio 40124 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      } } },
  Add = RTP4/$ {
    Media {
      LocalControl { Mode = SendReceive },
      Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      Remote {
v=0
c=IN IP4 172.40.0.100
m=audio 43922 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
} } } } }

- In above message, I expressed TerminationID as RTP2/$, RTP4/$.
   Is it possible to express ephemeral Termination as above?

Thank you in advance for your help.


_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
이경태 | 2 Nov 2005 15:06
Favicon

IP-IP TrFO call flow


Hi All.

I am making TrFO IP-IP call flow for IMS MGW.

I have some question.

- Are there packages for TrFO for IMS MGW?
- How about sdp attributes?
- where can I find TrFO IP-IP call flow for IMS MGW?
- I tried to make Add message for TrFO IP-IP call as following.
What do you think about this message?

MEGACO/1 [172.21.0.100]:2944
Transaction = 1000 {
Context = $ {
Add = RTP2/$ {
Media {
LocalControl { Mode = SendReceive },
Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
Remote {
v=0
c=IN IP4 172.30.0.100
m=audio 40124 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
} } },
Add = RTP4/$ {
Media {
LocalControl { Mode = SendReceive },
Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
Remote {
v=0
c=IN IP4 172.40.0.100
m=audio 43922 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
} } } } }

- In above message, I expressed TerminationID as RTP2/$, RTP4/$.
Is it possible to express ephemeral Termination as above?

Thank you in advance for your help.






_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
lkt | 3 Nov 2005 01:47
Favicon

TrFO IP-IP call flow for IMS MGW

Hi All.

I am making TrFO IP-IP call flow for IMS MGW.

I have some question.

- Are there packages for TrFO for IMS MGW?
- How about sdp attributes?
- where can I find TrFO IP-IP call flow for IMS MGW?
- I tried to make Add message for TrFO IP-IP call as following.
   What do you think about this message?

MEGACO/1 [172.21.0.100]:2944
Transaction = 1000 {
Context = $ {
  Add = RTP2/$ {
    Media {
      LocalControl { Mode = SendReceive },
      Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      Remote {
v=0
c=IN IP4 172.30.0.100
m=audio 40124 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      } } },
  Add = RTP4/$ {
    Media {
      LocalControl { Mode = SendReceive },
      Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 97
a=rtpmap:97 AMR/8000/1
      Remote {
v=0
c=IN IP4 172.40.0.100
m=audio 43922 RTP/AVP 97
a=rtpmap:97 AMR/8000/1
} } } } }

- In above message, I expressed TerminationID as RTP2/$, RTP4/$.
   Is it possible to express ephemeral Termination as above?

Thank you in advance for your help.


_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
Mayhan, Heather M [NTK] | 3 Nov 2005 23:16
Picon
Favicon

FW: Echo Cancellation




In a Megaco Modify Request, in the Package name, I see a reference to TDMC/EC=On.  This is to request Echo Cancellation be turned on.  However, in the reply, there is no reference to this portion of the Modify request.  My question is, should the gateway acknowledge the request for echo cancellation services, either by acknowledging it or denying it?

Thanks~

Heather

 

 

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
Wainwright, John | 7 Nov 2005 17:31
Picon

Signal 'play' failure

If as an MG I am unable to 'play' a signal requested by the MGC what error code should be returned ?  Is  510 "Insufficient Resources" the typical/expected response ?
Also,  should the MG take any other action such as possibly clearing up a termination or should it wait for further commands from the MGC. e.g. a user goes off-hook but dialtone could not be played for some reason.
 
Thanks
John
_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
Richard Sun | 7 Nov 2005 17:34
Picon
Favicon

TimeStamp format

In the defination of TimeStamp
yyyymmddThhmmssss
why ssss is 4-digit?

Does any MGC really make use of the TimeStamp
in the ObservedEventsDescriptor?

Thanks for any info.
-Richard
Permalink | Reply | 0 comments |
headers
Mayhan, Heather M [NTK] | 7 Nov 2005 17:35
Picon
Favicon

Number of Attributes in a MDCX

Is there a limit to the number of Attribute lines that can be in an MCDX message?

Heather M. Mayhan

Sprint-Nextel

NTAC-Voice Switching & Signaling

913-534-3679-Work

913-226-9731-Cell

 

 

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
Kevin Boyle | 7 Nov 2005 19:25
Favicon

RE: Number of Attributes in a MDCX

There are no MDCX Commands in Megaco/H.248.  You are thinking of MGCP,
which is handled on a different mailing list.

Kevin

________________________________

	From: megaco-bounces <at> ietf.org [mailto:megaco-bounces <at> ietf.org]
On Behalf Of Mayhan, Heather M [NTK]
	Sent: Monday, November 07, 2005 11:35 AM
	To: megaco <at> ietf.org
	Subject: [Megaco] Number of Attributes in a MDCX
	
	

	Is there a limit to the number of Attribute lines that can be in
an MCDX message?

	Heather M. Mayhan

	Sprint-Nextel

	NTAC-Voice Switching & Signaling

	913-534-3679-Work

	913-226-9731-Cell
Permalink | Reply | 0 comments |

Gmane