No way to check from SCP callbacks identity of peer
See original GitHub issueCurrently there is no way to know from within the SCP callbacks which peer is calling us, or even which association invoked this callback.
For the latter problem, I added in #97 the sop_class.ServiceClass
instance, which contains a reference to the association. However, neither the ServiceClass
handler, nor the Association
, keep a record of (for instance) the Calling AET.
One way to mend this, would be to keep the Calling AET inside the Association
object, and then pass the ServiceClass
object to all callbacks (I can draft a PR). Other suggestions?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Get the senders IP address. · Issue #54 · pydicom/pynetdicom
Hi, is there a way to find out the senders IP address? I made a little DICOM receiver application and I need to...
Read more >scp "lost connection" but ssh works fine - Super User
Had the same issue. If you did a minimal install of Centos, it only install the openssh and openssh-server packages but not the ......
Read more >SSH and SCP commands fail to execute after successful SSH ...
The fatal error is not due to cygwin sshd but to the W10 one as mentioned in the error message: C:\WINDOWS\SysWOW64\bsh\usr\sbin\sshd.exe.
Read more >TS 129 500 - V16.5.0 - 5G - ETSI
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical ...
Read more >scp does not work. Finding the cause - Unix Stack Exchange
debug1: Sending command: scp -v -d -t /tmp [...] debug2: exec request accepted on channel 0. SCP works by opening an SSH connection...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I added this functionality to the association, but apparently never set it up as a PR. You can see the implementation here: https://github.com/amosonn/pynetdicom3/commit/62b3b6d71eaab3a80f99bb1cade124f6df463ee6, I’ll try to wrap it up and submit it later. It belongs to my branch https://github.com/amosonn/pynetdicom3/tree/all_together , but I wouldn’t recommend working with it, I change it very often.
The calling AE title is now accessible via the
info
parameter that gets passed to the callback:info['requestor']['ae_title']
. The requestor’s port and IP address are also available.