Hi Jeff,
I attached a zip containing a wireshark trace and rtf logs. /den/cfs-file.ashx/__key/communityserver-discussions-components-files/7/7713.logs.zip
In this trace a HMP application located on 10.8.48.53 is register as extension 3006 with an Asterisk server at 10.8.32.22. After the 401 challenge, another SIP REGISTER is sent with Auth and registration is successful.
I am then able to ring in from extension 4007 > 3006 and navigate through the IVR. The application then triggers a call from it to 4101 (3006 > 4101). However when the Asterisk returns a 401 challenge to the INVITE, HMP only returns ACK and doesn't retry with Auth.
Also, from this point onwards, it is no longer possible to ring in via 3006 until the application is restarted, as if the application has de-registered.
Some things I notice are perhaps wrong:
In rtflog-LOCAL-20170606-12h02m50.247s.txt, line 1070
06/06/2017 12:02:57.250 5260 7144 gc_h3r SIP_RAS DEBG sip_register.cp:1195 ! 0 ! << SipRegCache::normalizeRequestURI - Successfully normalized Request-Uri: 'sip:3006;ttl=70'
Should the Request-Uri contain the ttl?
Also rtflog-LOCAL-20170606-12h02m50.247s.txt makes two references to "sip:10.8.32.22@10.8.48.53" on lines 1033 and 1083, which don't look valid
I've also found twice the windows service "DHCP Client" has locked access to the application exe, and I've had to restart that service. Some Dialogic services use this I know. I'm wondering if the problem relates to Dialogic trying to do a DNS lookup? We have multiple Asterisk PBX machines on our network. The name "asterisk" resolves to an Asterisk other than the one being used for registration here. No traffic I can see mentions the "asterisk" domain name (although Auth uses an "asterisk" realm), I have tried to add "asterisk" to the local hosts file so it points to the Asterisk I am actually using. This hasn't fixed anything though.
Any thoughts are welcome.
Thanks, Brendan