That gives me something to look at :). Nothing too obvious though… and no worries about the posted md5 password hash by the way. Can you make something out of this?
<— SIP read from UDP:192.168.1.117:57066 —>
ACK sip:1001@192.168.1.144:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.117:57066;branch=z9hG4bK-524287-1—5122ede860b625cd;rport
Max-Forwards: 70
Contact: sip:6002@192.168.1.117:57066;transport=UDP
To: sip:1001@192.168.1.144;transport=UDP;tag=as75d20db2
From: sip:6002@192.168.1.144;transport=UDP;tag=ef20c303
Call-ID: 1NBzvDjOnitpP_qSIuKL8A…
CSeq: 2 ACK
User-Agent: Zoiper rv2.8.6
Content-Length: 0
<------------->
— (10 headers 0 lines) —
– Executing [1001@internal:2] VoiceMailMain(“SIP/6002-00000014”, “7001”) in new stack
– <SIP/6002-00000014> Playing ‘vm-password.gsm’ (language ‘nl’)
– <SIP/6002-00000014> Playing ‘vm-youhave.gsm’ (language ‘nl’)
– <SIP/6002-00000014> Playing ‘digits/1.gsm’ (language ‘nl’)
== Spawn extension (internal, 1001, 2) exited non-zero on 'SIP/6002-00000014’
Scheduling destruction of SIP dialog ‘1NBzvDjOnitpP_qSIuKL8A…’ in 6400 ms (Method: ACK)
set_destination: Parsing sip:6002@192.168.1.117:57066;transport=UDP for address/port to send to
set_destination: set destination to 192.168.1.117:57066
Reliably Transmitting (no NAT) to 192.168.1.117:57066:
BYE sip:6002@192.168.1.117:57066;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.144:5060;branch=z9hG4bK55c95dab;rport
Max-Forwards: 70
From: sip:1001@192.168.1.144;transport=UDP;tag=as75d20db2
To: sip:6002@192.168.1.144;transport=UDP;tag=ef20c303
Call-ID: 1NBzvDjOnitpP_qSIuKL8A…
CSeq: 102 BYE
User-Agent: J.Vergouwe-PBX
Proxy-Authorization: Digest username=“6002”, realm=“asterisk”, algorithm=MD5, uri=“sip:192.168.1.144”, nonce=“6c170fb6”, response="873a6583b0d511615ca2021b23e05597"
X-Asterisk-HangupCause: Unknown
X-Asterisk-HangupCauseCode: 0
Content-Length: 0