Conference irocz::common_brouters

>We have a problem with private X.25 between a Routeabout Access EW and an 
>Ericsson HLR  (GSM Home Location Registry). The call is coming in, but is 
>rejected by the Routeabout with a cause code of 0 and diag code of 249.

	Is the incoming call for routing or are you using X.25 switching?

>We get an event saying "prot not supported" together with the clear event.
	
	This is a general "catch-all" for unrecognised/unwanted calls.	

>Is there any way to look into the call details using the EVL system on the RA?

	EVL does not print the details, only the basic packet types.
	If you are using LLC2/switching, then make sure you have X25S
	events switched on too.

>Is there any CTF-interface that could be run from an OpenVMS system connected 
>to the Ethernet side of the router?

	The router has support for DTF. DTF kits are available from:

	http://www.networks.digital.com:80/dr/dtf/dtf.html

	I would certainly switch on the X25 Switching events.

	The most likely cause (which would get logged by ELS) is
	with incompatible packet/window size between the X.25
	network and the LLC2 network.

	Unless you can get a DTF trace, it is difficult to say what might
	be happening.

	The fact that you see "protocol not supported" implies that the
	incoming call is not recognised as a candidate for switching and
	is getting passed to Routing. 

	This could be (at least) one of two things:

	The incoming call contains a user data field that matches a routing
	protocol. You could try increasing the switching filter priority
	to be higher than routing (255).

	Or, there is some basic problem with the client/filter definitions.
	Can you post configuration details?

  X25S Config>list client

  to-Thames       ENABLED  Ifc = 3  



  to-switch       ENABLED  Ifc = 1  


  X25S Config>



>> Is this a typo? It appears that you haven't associated the filters with
   their corresponding clients.