asterisk users - Dec 2006 - Is MOH Still Broken in Asterisk 1.4 (beta3)?

I'm wondering if moh is still broken in Asterisk 1.4 beta3. In Asterisk 1.2,
when a callee put a caller on hold, the musiconhold class that was played was
not the one the callee wanted the caller to hear, but something else. Even after
using mohsuggest in Asterisk 1.4, it still appears that this is not working
correctly.

Here's the results of a simple test:

CASE CALLER     CALLEE     HOLDER     HOLDER HEARS MOH
------------------------------------------------------
1    3254101    3254102    3254101    moh1
2    3254101    3254102    3254102    default

3    3254102    3254101    3254102    moh2
4    3254102    3254101    3254101    default

For each extension, I have mohsuggest set. Test cases 1 and 3, where the caller
puts the callee on hold, yield the expected behaviour. However, test cases 2 and
4 where the callee puts the caller on hold, do not yield the correct results.

Here's what the results SHOULD be.

CASE CALLER     CALLEE     HOLDER     HOLDER HEARS MOH
------------------------------------------------------
1    3254101    3254102    3254101    moh1
2    3254101    3254102    3254102    moh2

3    3254102    3254101    3254102    moh2
4    3254102    3254101    3254101    moh1

Am I possibly doing something wrong with mohsuggest?

sip.conf:

[general]
context=default
allowoverlap=no
bindport=5060
bindaddr=0.0.0.0
srvlookup=yes

[3254101]
type = friend 
context = CallStart
username = 3254101
accountcode = 3254101
qualify = yes
canreinvite = no
host = dynamic
dtmfmode = rfc2833
nat = no
callerid = Douglas Garstang <3254101>
secret = password
mohsuggest = moh1

[3254102]
type = friend 
context = CallStart
username = 3254102
accountcode = 3254102
qualify = yes
canreinvite = no
host = dynamic
dtmfmode = rfc2833
nat = no
callerid = Douglas Garstang <3254101>
secret = password
mohsuggest = moh2