HLS encryption VOD randomly stop playing on IOS

Question

We have 4 AMS servers load balanced (DNS) with identical application on each. RTMPe is playing fine from flash desktops, however, HLSe on IOS devices randomly stops playing part way through the content. I do not see any relevant errors in AMS/Apache. The front end player shows the following errors when the content stops playing:
"CoreMediaErrorDomain" "No response for media file in 0.49632s"
"CoreMediaErrorDomain" "Segment exceeds specified bandwidth for variant"
Similar issues discussed here: http://openradar.io/15060374 (thought not AMS specific).
This could be a player issue. It seems to randomly have issues grabbing an HLS segment. Has anyone else had any similar issues?
(the following IP's, certs, URL's have been replaced for privacy).
httpd.conf
<Location /hls-vod>
                HLSHttpStreamingEnabled true
                HLSMediaFileDuration 8000
                HttpStreamingContentPath "/mnt/store0/"
                HLSFmsDirPath ".."
                HLSJITConfAllowed true
                # Cache-control header configuration start
                # Specify the max-age(in secs) to set in the Cache-Control header
                # for different response types (m3u8, ts, drmmeta,...).
                # A value of -1 turns off setting the cache control header.
                HLSM3U8MaxAge 86400
                HLSTSSegmentMaxAge 86400
                HLSMetaMaxAge 3600
                # Cache-control header configuration end
                # Uncomment the following directives to enable encryption
                # for this location.
                     HLSEncryptionScope server
                     HLSEncryptCipherKeyFile "../creds/vodkey.bin"
                     HLSEncryptKeyURI        "https://myurl/hls-key/vodkey.bin"
                Options -Indexes FollowSymLinks
        </Location>
httpd-hls-secure.conf
<VirtualHost myip:443>
ServerName myserver
DocumentRoot "../webroot"
SSLEngine on
SSLCertificateFile    "/opt/certs/mycert.crt"
#Uncomment the following if the file specified above does not
#have the private key
SSLCertificateKeyFile "/opt/certs/mykey.key"
#Client Authentication configuration
#SSLVerifyClient require
#SSLVerifyDepth       9
SSLCACertificateFile "/opt/certs/myintermediate.crt"
SSLOptions           +StdEnvVars +FakeBasicAuth -ExportCertData +StrictRequire
<Location /hls-key>
  HLSEncryptHostCipherKey true
  HLSFmsDirPath ".."
  HLSEncryptKeyRepository "../creds"
  SSLRequireSSL
#  SSLRequire %{SSL_CLIENT_S_DN_CN} eq "iPhoneOS Device Certificate"
</Location>
</VirtualHost>

Answer 1

I just wanted to add an update in case anyone else runs into a similar issue.  I seem to have found a solution to the problem.  Here's what I did:
1) Plugged in to my computer and removed all music from my iPod (just unselected "sync music" then allowed the iPod to sync).
2) In iTunes, under the summary tab of my iPod, I selected "convert higher bit rate songs to 256 kbps AAC" in the options section.
3) I synced my iPod.  This took a REALLY long time, as I have just over 52GB of music that I chose to put on my iPod.  This is 52GB AFTER the conversion to 256kbps.  Anyway, it took a couple hours to sync the first time because it had to convert almost every song.  After the first sync, it doesn't take long to sync unless I add a lot of songs and even then, it only takes a few minutes.
I've listened to my music on a variety of devices (in my car, different types of headphones, computer at work etc) and haven't noticed any degradation in quality, despite the fact that nearly all of the original music files on my computer are 320kbps.  I'm not sure if the problem I was having was due to the higher bitrate or the fact that the original music files are a variety of formats (aac, mp3, wav, and some others).
I did this later in the evening after I posted the original question and have not had a problem since (about 15 days).  Skipping songs seems to go a lot faster as well.  I use my iPod a good 6-10 hours everyday, so I think that having no problems in the last 15 days is pretty good evidence that this is a good solution.
Hopefully this is helpful to anyone that stops by here