The Asterisk 1.4.x bug can be found here: http://bugs.digium.com/view.php?id=10323
This is fixed in Asterisk 1.4.10.
There is also a patch available for 1.4.9 available here: http://bugs.digium.com/file_download.php?file_id=14972&type=bug
If you don’t want to patch/upgrade you can add the following to sip_custom.conf
[code:1]notifyhold=no[/code:1]
I hope my understanding is correct but this is the situation as I see it. So from the freePBX side I do not believe anything should/could be done.
C.
I’ve been away from computers for a few days, been fitting a new bathroom, what a nightmare!
Taking a break from wet plaster and leaking pipes to check the forums! I will try applying asterisk 1.4.10 tomorrow and run tests, I imagine that will solve it for good.
I guess this simply goes to prove right those who say 1.4 is not ready yet.
Confirmed. Upgrade to asterisk 1.4.10 removes the issue.
The sip conf is back at defaults set by FreePBX and I’ve tried and tried to recreate the problem. It’s a fully squashed bug 
[quote=“dirk”]Confirmed. Upgrade to asterisk 1.4.10 removes the issue.
The sip conf is back at defaults set by FreePBX and I’ve tried and tried to recreate the problem. It’s a fully squashed bug :)[/quote]
Good stuff. Now the only problem I have with 1.4.10 is that it broke app_swift so I’m going to have to fallback to 1.4.9 