The WireShark in trace 0321_1607_vgEngine - Copy.zip captures a Trombone Transfer (Dial and Conference Transfer) attempt.
The outgoing leg of the '2-line tromboned' call transfer is rejected by Fortivoice PBX at 192.168.1.199 with a "407 - PROXY AUTHORIZATION REQUIRED".
This is because the CallerID was not set on the outgoing call leg - so the CallerID from the incoming call was re-used (firstname.lastname@example.org) - but as Fortivoice requests authentication before placing outgoing calls the outgoing call failed as VoiceGuide does not have authentication details for that relayed Caller ID.
You need to specify CallerID on outgoing calls that is one of the extensions that is registered by VoiceGuide.
This is done using the <CallerID> option in the VoiceGuide's Transfer module, or in the Config.xml file.
Once the outgoing CallerID is specified then the authentication on outgoing call will be made as well, and the outgoing leg of the call will be connected.
Easiest approach to set up the system is to just configure Fortivoice to accept incoming calls from VoiceGuide's IP 192.168.1.50
Basically setting up SIP trunk between VoiceGuide and Fortivoice.
This way Fortivoice will just accept all incoming calls from VoiceGuide's IP 192.168.1.50.
Another approach is:
You can setup an authentication that VoiceGuide can use with Fortivoice when sending calls to it. Then if VoiceGuide receives a 407 response from Fortivoice then VoiceGuide will re-issue the SIP invite to Fortivoice with the right authentication to let Fortivoice accept the call.
If you will setup a user on Fortivoice that VoiceGuide can use, then those details can be set in VoiceGuide's Config.xml file.
Please see: http://www.voiceguid...ip_register.htm
Then VoiceGuide will register itself with Fortivoice and authenticate any 407 responses.
As mentioned, its just easiest to set up a SIP trunk between VoiceGuide and Fortivoice, to have Fortivoice just accept all incoming calls from VoiceGuide's IP: 192.168.1.50