Re: Initiating X.25 calls

["Dean D. Throop" <[e-mail]>]

>From [e-mail]  Mon Jan 27 15:20:33 1992
>Message-Id: <[e-mail]>
>To: [e-mail]
>Cc: [e-mail], [e-mail]
>Subject:  Re:  Initiating X.25 calls
>
>>>I know that the IP over X.25 MIB specifies ioxConIpAddress, which can be
>>>translated into a destination X.25 address, but shouldn't the X.25 MIB
>>>provide a mechanism to directly configure calls?
>>
>>From my perspective, an X.25 virtual circuit is opened on behalf of a
>>client protocol.  It's the client that ought to know whom it's going to
>>communicate with, and therefore should provide the destination X.121
>>address for a call.
>
>I've only been following this thread loosely, so please forgive me if I
>missed the point here, but I thought that what Mark was looking for was a
>way to configure call setup facilities for specific X.121 addresses.
>This has been a very useful, if not necessary, thing to be able to do.
>Last IP-on-X.25 implementation I worked on, we had to set up calls with
>opposite-of-default facilities for calls to a certain PDN overseas.
>
>-Steve

The X.121 address to call for any session belongs to the upper layer
service asking X.25 to place a call.  To change that address, the
NMS must use the MIB for the upper layer service.

Dean Throop		[e-mail]