topic Re: X.25 access number change in Operating System - OpenVMS

X.25 access number change

Hans Jivesten — Mon, 15 Aug 2011 07:43:24 GMT

Hi,

I need to change the access number to reach our supplier from xxxxx1234 to xxxxx1256.

However they still want to contact us from xxxxx1234.

Now, I found three places where there current number is listed:

For X.25 config I found the following:

disable x25 access
create x25 access reachable address GXS addre prefi 36:xxxxxxxxxx1234:
set x25 access reachable address "gxs" dte class "xot-class-0"
set x25 access reachable address "gxs" mapping Manual
set x25 access reachable address "gxs" destination xxxxxxxxxx1234
set x25 access reachable address "gxs" address extensions False
enable x25 access

for MTA config I found:

set mta peer mta [type=manually configured, name="GXS"] -
presentation address "//""MARKIII""/NS+36xxxxxxxxxx1234,CONS"

Now to my question:

1, Which of the above lines do I need to change in order for us to contact them on xxxxxx1256 but they should still be able to call us from xxxxxx1234?

Any ideas are welcome. I have not been able to figure this out from reading the X.25 or Mailbus 400 (MTA) docs.

Kind regards,

Hans

Re: X.25 access number change

Buenaventura Acera — Tue, 16 Aug 2011 11:02:05 GMT

Hi Hans,

a lot of time since my last work with X.25 but I think you should modify all three entries as all of them are related to the local information needed to reach the remote destination.

Also, as far as I can see, you are not doing any specific filtering for incoming calls (X25 access filter statement) which could block remote connections based on the remote address (the default is to enable incoming call from any number) so they could continue using the original address to reach your system.

Regards,

Ventura

Re: X.25 access number change

Hans Jivesten — Tue, 16 Aug 2011 11:46:01 GMT

Hi Ventura,

Thank for your reply.

Aha, so that is what the filter statement is for. Sounds reasonable enough.

I thought that maybe the first line was for controlling incoming connections.

I'll go with your suggestion and post the result here.

Kind regards,

Hans

Re: X.25 access number change

Hans Jivesten — Mon, 29 Aug 2011 09:33:52 GMT

The above tip worked just fine.

We ran into other poblems though, but that's another story.

regards,

Hans

Re: X.25 access number change

black_cat — Tue, 30 Aug 2011 15:22:27 GMT

Hans,

having noticed that you are using an ancient version of the MTA I realized that the recent changes with respect to NSAP checking are not included in your version of the MTA.

That's why I would change your PEE MTA definitions to

set mta peer mta [type=manually configured, name="GXS"] -
presentationaddress "//""MARKIII""/NS+36xxxxxxxxxx1234,CONS|NS+36xxxxxxxxxx1236,CONS"

You may have to change the order such of the 2 NSAP addresses (above) such that the new one is initated first. The old one is only there to satisfy the NSAP validation that the MTA still does in your version.

If you have enabled the MTA events I imagine you should have seen MTA validation events.

Hope that helps.

John

Re: X.25 access number change

Hans Jivesten — Wed, 31 Aug 2011 09:26:33 GMT

John,

It turned out that our X.400 provider had indeed changed the number they are calling us from to the new number xxxx1256. Changing all three instances, shown in my original post, to the new number worked just fine.

However, we then ran into problem between our system and theirs such as our MTA reported a Protocol Violation, which we are still trying to figure out. In the mean time we are routed back to their old environment.

Regards,
Hans