This is an old issue on which you can seach and find info. Some info
indicates that you need a timing source such as a zaptel card or
ztdummy. Other suggests that if you are using native music on hold and
mpg123 is in the path you might run into this error.
MARK.
Daniel Corbe wrote:
Has anyone run into this problem yet?
-Daniel
On 9/9/05, Daniel Corbe <[EMAIL PROTECTED]> wrote:
I'm getting a FLOOD of these types of messages on my MAC OS X box:
Sep 9 14:46:31 NOTICE[17627]: res_musiconhold.c:493 monmp3thread:
Request to schedule in the past?!?!
Sep 9 14:46:37 NOTICE[17627]: res_musiconhold.c:493 monmp3thread:
Request to schedule in the past?!?!
Sep 9 14:46:37 NOTICE[17627]: res_musiconhold.c:493 monmp3thread:
Request to schedule in the past?!?!
Sep 9 14:46:43 NOTICE[17627]: res_musiconhold.c:493 monmp3thread:
Request to schedule in the past?!?!
-Daniel
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
