Re: Media flow managed by 2 terminations

Thanks Javi for sharing that detailed background!

Indeed, option 3 would be not possible, I quite agree. Option 3 did suppose a single "media flow" component,
but not two as in your considered use case.

I could imagine that single-stream-per-termination structures, i.e., dedicated H.248 IP terminations
for  PH and FH traffic, might be beneficial, e.g. from perspective of "unsuccessful call handling" like
for instance
- H.248.40 for monitoring activity of the media flows on IP side,
- H.248.36 for detection of hanging IP terminations,
- etc.

-Albrecht  

> -----Original Message-----
> From: megaco-bounces <at> ietf.org 
> [mailto:megaco-bounces <at> ietf.org] On Behalf Of Javi
> Sent: Freitag, 29. Juli 2011 13:46
> To: megaco <at> ietf.org
> Subject: Re: [Megaco] Media flow managed by 2 terminations
> 
> Albrecht,
> 
> The entire network picture is similar to "ETSI_ARGW[TS 183 
> 002 v3.3.1]/Clause 7.3.2" or "draft-bouwen-megaco-isdn-data-00":
> 
> ISDN TE <-> AGW (MG) <-> PH or FH <-> PSPDN
> 
> where PH "Packet Handler" and FH "Frame Handler" are 
> different equipments (I propose a descomposal architecture 
(Continue reading)

Cool..AkaSh | 17 Aug 15:35 2011
Picon

Query about LATCH Vs RELATCH

Hi,

 

I have a query about the difference between Latch and Relatch. I am testing BGF, and in my scenario when Latch is followed by Relatch then it is working fine i.e. first it learn the packets from the source IP (except remote descriptor IP) and when did RELATCH then learned the packets from new source IP and drops the packets from the previous IP.

Now when I am doing a scenario Latch followed by Latch then also first it learns the packets from the source IP and when did LATCH then it learn the packet from new source IP and drops the packets from previous IP.

 

Here I am not able to figure out what is the difference between Latch and Relatch because in the above scenario I can see LATCH is doing the same thing which RELATCH does. Why RELATCH comes into the picture?

 

Please help me to figure out this, so that can proceed. Your help would be appreciable.

 

 

 

---

Thanks & Regards,

Akash Gupta






_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www.ietf.org/mailman/listinfo/megaco
Makaraju, Maridi Raju (Raju | 17 Aug 21:35 2011

Re: Query about LATCH Vs RELATCH

Akash,

Latch completes when very next pkt arrives irrespective of the src is new or same as before.
Whereas relatch completes only when pkt from new src arrives.
In one scenario it may so happen that the next pkt arrives from new src. In such case eithet a latch or relatch
can be completed with the same effect.

Thanks
Raju

 -----Original Message-----
From: 	Cool..AkaSh [mailto:akashclose2u <at> gmail.com]
Sent:	Wednesday, August 17, 2011 12:18 PM Central Standard Time
To:	Megaco <at> ietf.org
Subject:	[Megaco] Query about LATCH Vs RELATCH

Hi,

I have a query about the difference between Latch and Relatch. I am testing BGF, and in my scenario when Latch
is followed by Relatch then it is working fine i.e. first it learn the packets from the source IP (except
remote descriptor IP) and when did RELATCH then learned the packets from new source IP and drops the
packets from the previous IP.

Now when I am doing a scenario Latch followed by Latch then also first it learns the packets from the source IP
and when did LATCH then it learn the packet from new source IP and drops the packets from previous IP.

Here I am not able to figure out what is the difference between Latch and Relatch because in the above
scenario I can see LATCH is doing the same thing which RELATCH does. Why RELATCH comes into the picture? 

Please help me to figure out this, so that can proceed. Your help would be appreciable.

---

Thanks & Regards,

Akash Gupta

Gmane