DICOM File Not Sending From Local To Orthanc Server

[salim.d...@gmail.com]

I ma trying to send DICOM file to the Orthanc Server but could not send.

I am using OrthancPeers and also tried DicomModalities

Using following curl command:

curl -X POST http://127.0.0.1/peers/peer2/store -b f4160570-1c76d8c0-11a1550c-7eb59b52-a41abf23

[Thibault Nélis]

Hello,

-b is for cookies, you'll want to use --data-binary (although in this
case -d should work too).
--
Thibault Nélis <t...@osimis.io>
Osimis

[salim.d...@gmail.com]

-d is also not working through REST API, also tried using OSIMIS to send file to remote Orthanc Server throws error "Error during store".

[Thibault Nélis]

On Thu, 2017-05-11 at 04:28 -0700, salim.d...@gmail.com wrote:
> -d is also not working through REST API, also tried using OSIMIS to
> send file to remote Orthanc Server throws error "Error during store".

I'm attaching a sample Docker-based setup and curl-based procedure to
transfer a file via Orthanc peering. I invite you to compare it with
your setup.

If you can't find the source of the problem, please send us your
Orthanc configuration files, full logs, and possibly the DICOM data
you're trying to transfer.

Hope this helps,
--
Thibault Nélis <t...@osimis.io>
Osimis.

[salim.d...@gmail.com]

I was running version 1 but wasn't able to send DICOM file to remote peer so i cloned version-2 of Orthanc but was unable to install using Docker-composer.

The error i am getting while building with composer:

$ docker-compose up --build -d
Builds, (re)creates, starts, and attaches to containers for a service.

Unless they are already running, this command also starts any linked services.

The `docker-compose up` command aggregates the output of each container. When
the command exits, all containers are stopped. Running `docker-compose up -d`
starts the containers in the background and leaves them running.

If there are existing containers for a service, and the service's configuration
or image was changed after the container's creation, `docker-compose up` picks
up the changes by stopping and recreating the containers (preserving mounted
volumes). To prevent Compose from picking up changes, use the `--no-recreate`
flag.

If you want to force Compose to stop and recreate all containers, use the
`--force-recreate` flag.

Usage: up [options] [SERVICE...]

Options:
--allow-insecure-ssl Deprecated - no effect.
-d Detached mode: Run containers in the background,
print new container names.
--no-color Produce monochrome output.
--no-deps Don't start linked services.
--force-recreate Recreate containers even if their configuration and
image haven't changed. Incompatible with --no-recreate.
--no-recreate If containers already exist, don't recreate them.
Incompatible with --force-recreate.
--no-build Don't build an image, even if it's missing
-t, --timeout TIMEOUT Use this timeout in seconds for container shutdown
when attached or when containers are already
running. (default: 10)

[Thibault Nélis]

On Thu, 2017-05-11 at 22:59 -0700, salim.d...@gmail.com wrote:
> I was running version 1 but wasn't able to send DICOM file to remote
> peer so i cloned version-2 of Orthanc but was unable to install using
> Docker-composer.

Do you mean Orthanc 1.1 and Orthanc 1.2?

> The error i am getting while building with composer:
>
> $ docker-compose up --build  -d
> Builds, (re)creates, starts, and attaches to containers for a

> service. [...]

This actually doesn't really look like an error but the output of
docker-compose up --help.

Can you ensure there is no weird aliasing going on?

If it reads something like the following you're good:

(bash)
$ type docker-compose
docker-compose is hashed (/usr/bin/docker-compose)

It it reads something like the following then it might explain it:

(bash)
$ type ls
ls is aliased to `ls --color=auto'

Otherwise make sure you're in a directory with a `docker-compose.yml`
file in it. Maybe specify its path explicitly with `docker-compose --
file abc.yml up`. Check that your version of compose is reasonably
recent `docker-compose -v`. Finally, try with another, simpler sample
docker-compose file. If this fails then I encourage you to seek help in
Docker support channels (orthanc-users would probably not be the most
helpful place).

Hope this helps a bit,

[salim.d...@gmail.com]

Thanks for support

[Sébastien Jodogne]

Hello,

Back to your original post:

To send one DICOM file (say, "HelloWorld.dcm") to one Orthanc server with curl through the REST API, here is the correct command-line: 

# curl -X POST http://localhost:8042/instances --data-binary @HelloWorld.dcm

Note the "@" argument. This is explained in the Orthanc Book:

http://book.orthanc-server.com/users/rest.html#sending-dicom-images

HTH,

Sébastien-

[salim.d...@gmail.com]

Hello,

I am trying to send DICOM file from local othanc storage to the server not directly send the file

[Sébastien Jodogne]

Hello,

Here is a functional, minimalist sample. Start a first instance of Orthanc, with the following configuration file:

{

  "IndexDirectory" : "/tmp/a",

  "StorageDirectory" : "/tmp/a",

  "DicomModalities" : {

    "sample" : [ "ORTHANC", "localhost", 4343 ]

  },

  "OrthancPeers" : {

    "peer" : [ "http://localhost:8043/" ]

  }

}

Start a second instance of Orthanc, with this configuration:

{

  "IndexDirectory" : "/tmp/b",

  "StorageDirectory" : "/tmp/b",

  "DicomPort" : 4343,

  "HttpPort" : 8043

}

Given the configurations above, to transmit using the DICOM protocol an instance with Orthanc ID "b70601e7-9d088f26-caf39279-9b06a18b-1cd5b053", type:

# curl -X POST http://localhost:8042/modalities/sample/store -d b70601e7-9d088f26-caf39279-9b06a18b-1cd5b053

To transmit the same instance using the Orthanc REST API, type:

# curl -X POST http://localhost:8042/peers/peer/store -d b70601e7-9d088f26-caf39279-9b06a18b-1cd5b053

HTH,

Sébastien-