installation problems

kinomakino · Post by **kinomakino** » Fri Mar 20, 2009 8:32 am

HELLO, AT THE FIRST OF ALL, THANKS.

I´M FIGHTING WITH THE PACSONE INSTALLATION AND I´M JUST FINISHED.

NOW, I ´M LOST WITH MY CONFIGURATION.
THE SCENARIO IS THAT:

I CREATE AN AE . THIS IS AN EFILM SERVER WHO RECEIVED THE DICOM IMAGES FROM AN AGFA MACHINE.

I CAN´T GET ANY IMAGES STORED IN EFILM, SINCE PACSONE.

HOW CAN IN CONFIGURE THAT, BECAUSE A HAVE PING FROM PACSONE TO EFILM. I M THINKINK ABOUT I HAVE A WRONG CONFIGURATION.

THANKS TO ALL.

Post by **pacsone** » Fri Mar 20, 2009 3:45 pm

How are you sending images to eFilm, e.g., from the input modalities or from PacsOne Server?

kinomakino · Post by **kinomakino** » Fri Mar 20, 2009 5:10 pm

Sorry i m spanish and in bberry.
The escenario is. Agfa machine ------efilm. ( all my pacs is efilm. Storage. View. All) nos i m evaluating pacs one. I want to duplicate into pacs one the efilm estudies.
To the pacs one. When i try the system. Kill efilm and only use agfa and pacs one.
I dont configure nothing. No routing. No storage. Only ae config. (i only have dicom ping. Between efilm. And pacs one)

Post by **pacsone** » Fri Mar 20, 2009 6:17 pm

Your English is quite fine

So are you sending images from Agfa to PacsOne (with eFilm stopped)? If so, then it makes sense the images won't show up in eFilm because it has been stopped, and it is PacsOne Server that is receiving the images, i.e., only one of them (PacsOne or eFilm) can receive images from the same port.

kinomakino · Post by **kinomakino** » Fri Mar 20, 2009 8:05 pm

Thanks.

Don t understand me.

Now i send agfa to efilm. I want send efilm to pacs one. This is possible?.like relay.
If in a few dAys all will be good, kill efilm.

Post by **pacsone** » Fri Mar 20, 2009 8:14 pm

Yes, you can certainly setup an automatic routing rule in PacsOne Server to forward any images received from Agfa to eFilm, i.e., Agfa-->PacsOne-->eFilm.

Simply add an AE entry for eFilm in the Application Entity table of PacsOne Server with its AE Title, IP address and TCP port, then click on Auto Route and create a routing rule to forward any images received from the Agfa AE to the eFilm AE.

kinomakino · Post by **kinomakino** » Fri Mar 20, 2009 8:28 pm

I must learn english.

XD
Agfa to efilm to pacs. How?

Post by **pacsone** » Fri Mar 20, 2009 8:39 pm

No, it's Agfa to PacsOne to eFilm, not Agfa to eFilm to PacsOne.

Sending images from Agfa to PacsOne should be the same as sending to eFilm, then you can define the automatic routing rule on PacsOne Server to forward any images received from Agfa to eFilm.

kinomakino · Post by **kinomakino** » Fri Mar 20, 2009 8:42 pm

Thanks a lot.

kinomakino · Post by **kinomakino** » Mon Mar 23, 2009 1:36 pm

well, monday, working... a lot of problem xD.

Now, i kill mi efilm configuration from my AGFA MACHINE.
I configure AE objects like PACSONE (my server)
In PACSONE i configured my agfa machine.
now, i have tcp/ip PING, but not DICOM PING.

these are the errors.
thanks a lot.

agfa error

pacsone config.

pacsone error when make ECHO.

Warning: fsockopen() [function.fsockopen]: unable to connect to 192.168.0.212:104 (Se produjo un error durante el intento de conexión ya que la parte conectada no respondió adecuadamente tras un periodo de tiempo, o bien se produjo un error en la conexión establecida ya que el host conectado no ha podido responder. ) in C:\Archivos de programa\PacsOne\php\dicom.php on line 2441
fsockopen() failed: Se produjo un error durante el intento de conexión ya que la parte conectada no respondió adecuadamente tras un periodo de tiempo, o bien se produjo un error en la conexión establecida ya que el host conectado no ha podido responder. (10060)

Post by **pacsone** » Mon Mar 23, 2009 4:15 pm

There seems to be 2 separate issues:

1. The Dicom Echo from Agfa to PacsOne:

The Agfa device was sending a Dicom C-ECHO to Port 104 at the hostname of BARCELONA, so did you configure PacsOne Server to be running at Port 104 on this host of BARCELONA? If not sure, you can login to the PacsOne Server database and click on the Dicom AE link from the Main Menu, which will display the TCP port currently configured for PacsOne.

2. The Dicom Echo from PacsOne to this NXMC AE:

It seems that PacsOne can IP ping the hostname of NXMC, but the Dicom C-ECHO to Port 104 at this host has failed. So can you check if there is actually any Dicom application listening to Port 104 at this NXMC host, or if there is a firewall blocking inbound packets to Port 104 on this host?

One quick way to find out is to run the Telnet command to try to connect to Port 104 at this host:

Code: Select all

C:\>telnet NXMC 104

If the Telnet cannot connect to Port 104 at this hostname, then either there is no application listening to Port 104 on this host, or there's a firewall blocking inbound packets to Port 104 of this hostname.

kinomakino · Post by **kinomakino** » Mon Mar 23, 2009 5:49 pm

i think this is different.

i restore a backup from this morning.

only agfa nx with efilm working ( booth configurated in 104 port).

telnet to efilm port 104 is good.
telnet to agfa port 104 is NOT GOOD.

repeat, all is working.

Post by **pacsone** » Mon Mar 23, 2009 6:04 pm

kinomakino wrote: telnet to efilm port 104 is good.
telnet to agfa port 104 is NOT GOOD.

This seems to suggest that either Agfa was not listening to Port 104 on this "NXMC" host, or there's a firewall blocking inbound packets to Port 104 on this "NXMC" host.

For the Dicom Echo from Agfa to PacsOne, you need to make sure you've added an entry for the AE Title of the Agfa device ("NXMC") in the Application Entity page of PacsOne Server. Otherwise, PacsOne will reject association requests from the Agfa device since it's AE Title is unknown to PacsOne.