Hi there
Without a SIP trace, I can't say what the international call issue you mention might be but I think it is unlikely to have anything to do with the sipsak trunk entry. The sipsak entry was added in 109/110 for Pacemaker/crm. The Asterisk resource agent in Pacemaker uses sipsak to "ping" asterisk with a SIP OPTIONS request every few seconds to see if it is up and responding to sip requests. The trunk is not reported by the SAIL front-end, it just acts as an anchor point for the sipsak requests. What you should see in sark_sip_main is something like this
[sipsak]
type=peer
host={local host ip}
The host ip would normally be the local ip of the asterisk box (unless you are running Pacemaker, in which case it would be the Virtual IP, which you will find in globals=>haclusterip). If it isn't showing up as the local ip, it may be that the box is not using eth0. In either case it should be benign. The actual entry is generated at line 88 in the sip generator (/opt/sark/generator/sipSQL.php) so you can comment it out if you like. On reflection, perhaps we should suppress it for non Pacemaker installs.
If you'd like me to look at the International call issue then I'll need a console log of a failing call and a SIP trace.
You can always see what changes we've made in any new release by looking at the changelog
rpm -q sail --changelog | less
Kind Regards
S