Cell Relay Archive

[mukul@trillium.com (Mukul Katiyar)]

> 
> 
> 


> Hi Mukul,
> > > 
> > > Hi Ronald,
> > > 
> > > If you are doing your signaling in some VPI (say 10) other than the
> > > default VPI 0, then then data VCC should also be created in the same
> > > VPI (10) in which signaling is done. This is called associated
> > > signaling. 
> > 
> > Associated signalling has nothing to do with the VPI of the
> signalling channel,
> > Associated signalling is one, for which the signalling VC signals
> for all the VCs
> > in the given VP only and for no other VC not present within the VP
> carrying the
> > signalling VC. 
> >
> 


>   You are right. But what I tried to explain in my earlier mail is
> that in UNI3.1 or UNI4.0, 

>signaling VC can only be 0,5. You can use
> some other VP as Signaling VC only in PNNI Signaling that too only in
> the case of associated signaling. UNI doesn't allow any signaling VC
> other than 0,5.

 For UNI4.0 also one can use signalling VC as x,5 where x need not be 0.
 
 One is not allowed associated signalling in UNI4.0, but surely signalling
 can be performed on a Virtual Channel 5, within any virtual path that is
 supported by the given UNI. One can also have multiple signalling channels,
 controlling signalling for different virtual paths over the same UNI. Of
  course the Virtual path range to be controlled by each signalling 
 channel has to be understood by both the peer entities. 
 
 This provides UNI4.0 the capability of supporting virtual UNI and proxy signalling.



 Q.2931 is a UNI standard and it does allow for associted signalling also
 in addition to choice of using signalling channel within other virtual paths.
 
 Regards
 -mukul
  

>  
> > You can have the signalling channel within the VP numbered VPI-10
> and still perform
> > the signalling for VCs beyond those within the VPI-10, or for a
> group of
> > VPs, or even for all the VCs.
> > 
> > 
> > 
> > > 
> > > This associated signaling what you have asked, is not allowed in
> > > UNI3.1 and UNI4.0. This is allowed only in PNNI Signaling right now.
> > 
> > True Q.2931 and PNNI supports associated signalling.
> > 
> > 
> > _______________________________________
> > 
> > On Thu, 23 Jul 1998, Ronald Yap wrote:
> > 
> > > Hi Folks,
> > > 
> > > I have a basic question on UNI3.1/UNI4.0...
> > > 
> > > If I create a PVP (vpi=10) and enable UNI signalling on that path,
> will all
> > > subsiquent data-VCC created (via signalling) contained within the
> same PVP??
> > 
> >  The problem with this configuration is that at the access switch
> the VPC ( irrespective 
> >  of SVPC or PVPC) shall be completely switched to the egress port, 
> >  not giving the signalling entity to look into the signalling
> messages flowing through the
> >  signalling channel within this VP. 
> >  
> >  You shall not be able to signal for any VC within the VP far aside
> outside the VP that has been
> >  configured to PVP, with the standard implementation of signalling
> protocols. 
> >  Yes but an end to end signalling should be possible with the either
> ends understanding the 
> >  proprietry VP/VC assignments for each call, 
> > 
> > > 
> > > Is this specified in the standard documents? Or can the data-VCC
> be on
> > > different PVPs?
> > > 
> > > Please advice...thanks.
> > > /ronald
> > >