Basic question

DallasRT · Post by **DallasRT** » Tue Mar 07, 2006 5:06 pm

When you first install PacOne you are asked to input your AE. Is this a new AE solely for PacsOne or an exsisting AE?

The reason I ask is because I can ping to an AE host in Pacsone, but it does not download any of the images to the default directory. However, I am also using K-Pacs (sorry pacsone folks), that can see the images and recieve them with no problem. I am also careful to no load K-Pacs server when PacsOne is running.

We have a CT Twin that is sendind the data through a program called Passport, which converts the Elscint to DICOM images. The information is sent to a static ip and subnet on the Pacsone server.

As I stated earlier, with K-Pacs running the system sends the images over to the server and we can view them. However, if PacsOne is running, it just sits there and does not even acknowledge anything.

I am sure this is something on our part and NOT PacsOne software. So, please help a newbie out.

Post by **pacsone** » Wed Mar 08, 2006 2:42 am

The AE Title should be unique for each application entity, either for PacsOne or K-PACS.

Did you get any error from the CT when you send images to PacsOne?

DallasRT · Post by **DallasRT** » Wed Mar 08, 2006 5:26 am

pacsone wrote:The AE Title should be unique for each application entity, either for PacsOne or K-PACS.

Did you get any error from the CT when you send images to PacsOne?

When PacsOne is running, the CT's Passport begins to beep, this tell me that images are in que trying to be pushed, but it does not see the host. In this case, it does not see a AE called PacsOne.

In the Passport software there is a file called dicom.cfg where you put the host and user that the system will talk too. We have all the info in there for the Pacsone server, but it just does not seem to see it.

However, when K-Pacs dicom server loads, the system see it and begins to push the images to the Pacsone server. Of course none of the images are loaded into the mysql database or show up under the PacsOne interface. This is frustrating to say the least.

Any info you need like ipconfig or system please ask. I like what your software can do for our small hospital (32 bed...I did say small...)and have obtained approval to purchase, but I do not want to have to justify to my boss why we bought something that will not work.

*EDIT*

I know your software works, it has to be something we are neglecting to do on our side. Anyway, thanks for your help.

Post by **pacsone** » Wed Mar 08, 2006 1:13 pm

In order for 2 Dicom application to communicate to each other, you need to configure both ends:

1. From the Passport software side, when you configure the dicom.cfg file, did you add the configuration information for PacsOne? e.g., the AE Title assigned for PacsOne, the hostname/IP address where PacsOne is located, and the TCP port PacsOne listens to. If so, is there any diagnostic tool on this Passport software to verify the connection with a configured remote AE? e.g., can you try a Dicom Ping (C-ECHO) from this Passport software?

2. From the PacsOne Server side, you need to configure an AE for Passport by adding an AE in the Application Entity page, with the following information:

The AE Title for Passport
Hostname/IP address where Passsport is located
TCP port which Passport listens to (if it can accept Dicom connections)
The archive directory to store images received from Passport (otherwise the default archive directory will be used)

After adding the Passport AE, you can verify the Dicom connection by clicking on Ping link from the Application Entity page. This will verify the connection from PacsOne Server to Passport (uni-direction).

Only after both of the above steps have been configured and verified from both ends, then you can assert a successful Dicom connection link between the two entities.

DallasRT · Post by **DallasRT** » Thu Mar 09, 2006 5:41 am

pacsone wrote: did you add the configuration information for PacsOne? e.g., the AE Title assigned for PacsOne, the hostname/IP address....

I thought Pacsone just listened at the port (1234) for the dicom. This system has 3 NIC interfaces

eth0 - Dedicated DSL line
eth1 - Ethernet connection to PassPort
eth3 - Etthernet hub

How do you tell PacsOne to use a specific IP? Currently when we pull up the home.php it is using the DSL ip.
In IIS the default website ip is the DSL ip.

DallasRT · Post by **DallasRT** » Thu Mar 09, 2006 8:34 am

DallasRT wrote:
pacsone wrote: did you add the configuration information for PacsOne? e.g., the AE Title assigned for PacsOne, the hostname/IP address....
I thought Pacsone just listened at the port (1234) for the dicom. This system has 3 NIC interfaces

eth0 - Dedicated DSL line
eth1 - Ethernet connection to PassPort
eth3 - Etthernet hub

How do you tell PacsOne to use a specific IP? Currently when we pull up the home.php it is using the DSL ip.
In IIS the default website ip is the DSL ip.

Nevermind, we got it to finally work and recieve the images!
Now to be able to view them over the web, which is why we bought RemotEye.

If during the inital test everything is great, then we will definitley be buying!

Thanks

Post by **pacsone** » Thu Mar 09, 2006 1:02 pm

DallasRT wrote: I thought Pacsone just listened at the port (1234) for the dicom. This system has 3 NIC interfaces

eth0 - Dedicated DSL line
eth1 - Ethernet connection to PassPort
eth3 - Etthernet hub

How do you tell PacsOne to use a specific IP? Currently when we pull up the home.php it is using the DSL ip.
In IIS the default website ip is the DSL ip.

Good to hear you got it working.

For your question above, it does not matter which interface (eth0, eth1, eth2, etc.) from which the incoming packets are received, as long as the packets reached this host and PacsOne Server is listening to port 1234 on this host, these packets will be received by PacsOne Server.