> this is related to your carrier's SIP messages as they are sending a > sendonly attribute instead of sendrecv (taking a wild guess here) your > asterisk will act as if the call was placed on hold thus the MOH butts in. > an sip debug log for a similar call will be more helpful?
Thanks for the answer Tarek! I will try to obtain a full SIP trace tonight. If the problem is indeed that the carrier is sending the sendonly attribute in the SDP instead of sendrecv, what can I do? Is there anything I can configure on my side? Thanks again, Alex -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
