<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="9351" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://declassified.library.utoronto.ca/items/show/9351?output=omeka-xml" accessDate="2026-09-10T10:19:59-04:00">
  <fileContainer>
    <file fileId="6280">
      <src>https://declassified.library.utoronto.ca/files/original/672276d6967bb87064116091cd504ec1.pdf</src>
      <authentication>9c133ba80146f1c323098bcab09948e1</authentication>
      <elementSetContainer>
        <elementSet elementSetId="31">
          <name>PDF Text</name>
          <description/>
          <elementContainer>
            <element elementId="131">
              <name>Text</name>
              <description/>
              <elementTextContainer>
                <elementText elementTextId="85708">
                  <text>-

.—..

.

Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur faeces a I'information

C O P Y

.%

10th Maroh 1961.

Dear Mr. Bowie,
When Griffith and I were in Paris In January we discussed a
proposal which we are exploring on behalf of our Foreign Office.
I wa3 very sorry to hear that Griffith had been taken ill on his
Journey to Wellington and hope he Is doing well now. In the circumstances I am addressing this follow-up letter to you, going
Into some detail. Your letter of 24th June I960 referred to the
same basic idea.
2.
Our Foreign Offioe see the need for occasional but rapid
setting up of a telex call between their London Communications
Centre and Leitrim to supplement the existing leased circuit.
They require such calls to be set up In an overall period of 5
rainute3 from the moment that It is demanded In either Leitrim or
London.
3.
The Foreign Office already have a telex Installation connected
to our London automatic exchange. We do not intend that the
customer should dial from his telex instrument to call our telex
switchboard; in view of tho special attention that will have to
be given to establio . the call wlth..y E„ time limit, we would
arrange for the Foreign Office to telephone the booking to a
supervisor in the telex exchange, who would p'i&gt; . the requirement
with one of our switchboard operators and ensu: that he obtained
a Montreal channel expeditiously (it may becom.. a. "ssary to
break down an existing call). In order to avoid a*.; lengthy explanation from our operator, ho would merely ask yours for a
readily recognised number (which would be for you to suggest e.g.
Montreal 9999, or Leitrim 1234). This would, we hope, be sufficient
for your operator to initiate action to appropriate one of your
two Montreal-Leitrim lines, normally used in conjunction with the
leased circuit, to extend the call from London to .... i customer's
premises at Leitrim.
4.
As an overlapping opemtion, our London operator ould also
obtain the Foreign Office *.lex connection on the local side of
the cord circuit. We would expect the Foreign Office _-o ensure
that their telex machine was not busied for any other purpose
while this was going on.
5.
We would expect to complete our side of the operation (London
to Montreal) within 2-J minutes and would be gle . to have confirmation from you of Griffith's belle-' that your p ople could see
the call through to Leitrim in a similar period of time, making
a total of 5 minutes at the most. Could you al'o let me have a
description of the arrangements you will be maklne, so that I
can talk knowledgeably with our Foroign Office? In particular
could you outline any rearrangement... of equipment at* Leitrim
which may be necessary each time a tolex call of this nature Is
set up, so that the Foreign Office can understand what has to be
done and include it in the drill?
6.
I understand that there Is a similar requi. ?nt for calls
originated at Leitrim and I should be pleased tc .y*r how you would
propose to-organise this. Ho very special arrangements would be
necessary In London, as our operator on answering th call for the
Foreign Office's London number from Montreal would simply dial
that number and complete the connection. If necessary, the called
number would be preceded by some code word or "Priority for
".
Here again, Leitrim would tell the Foreign Office on the leased
circuit that this telex call v;as about to be established and it
icould be up to the Foreign Office to see that their telex line
was kept clear pending receipt of the transatlantic telex call.
D.F. Bowie Esq.,
Canadian Overseas Telecommunication Corporation.

2

000029

�Document disclosed under the Access to Information Act Document divulgue en vertu de la Loi sur faeces a I'information

-

2 -

7.
In replying to the queries In para3 5 and 6, could you also
please let ma know when you would be ready to undertake some test
calls from subscriber to subscriber (which would, we suggest, be
on a free basis) to establish whether the 5 minute target oould
be consistently achieved.. Subae;_u©_it 'exercise' calls by the
subscribers to satisfy themselves chat the facility could still
be used in times of real need, would be on the basis of paid
telex calls. I would barao3tgrateful If &lt; a could now settle this
quickly as the Foreign Office are getting inpatient with us.
Yours sincerely,

(G.H. COA'-ES)

000030

�</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </file>
  </fileContainer>
  <collection collectionId="72">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="71973">
                <text>Hydra</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="80007">
              <text>HY00224</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80010">
              <text>[Foreign Office Telex Connection] </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80013">
              <text>03/10/1961</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="80016">
              <text>Hydra Communications - Policy, RG24, 1250-36 Vol. 2, Library and Archives Canada (LAC) </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80019">
              <text>Department of National Defence</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80022">
              <text>Canadian Crown</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80025">
              <text>DND, External Affairs, Tripartite Alerts, transatlantic cables, emergency planning, emergency communications </text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80028">
              <text>Material duplicated in &lt;a href="https://declassified.library.utoronto.ca/items/show/9048" target="_blank" rel="noopener"&gt;HY00123&lt;/a&gt;.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="80031">
              <text>Canada Declassified</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80034">
              <text>Text</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80037">
              <text>PDF</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80040">
              <text>en</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
