|Summary:||ASTERISK-00327: No audio with CVS 09/28/03|
|Date Opened:||2003-09-28 22:32:36||Date Closed:||2011-06-07 14:05:14|
|Description:||CVS 09/28/03 produces no audio. This is for MOH, Playback, Background and bridged channels. No change to any confs. |
Reverted back and works.
****** ADDITIONAL INFORMATION ******
Executing Answer("SIP/phone102-6c63", "") in new stack
-- Executing DigitTimeout("SIP/phone102-6c63", "5") in new stack
-- Set Digit Timeout to 5
-- Executing ResponseTimeout("SIP/phone102-6c63", "10") in new stack
-- Set Response Timeout to 10
-- Executing BackGround("SIP/phone102-6c63", "intro-ar") in new stack
-- Playing 'intro-ar'
-- Executing BackGround("SIP/phone102-6c63", "intro-en") in new stack
-- Playing 'intro-en'
Executing Dial("SIP/phone101-f025", "SIP/phone11|20|tr") in new stack
-- Called phone11
-- SIP/phone11-d8c1 is ringing
-- SIP/phone11-d8c1 answered SIP/phone101-f025
-- Attempting native bridge of SIP/phone101-f025 and SIP/phone11-d8c1
No sound on either above examples.
Always get this message when "shutdown now" is executed
Yuck! Error in buffer handling...: Success (might not be related)
|Comments:||By: Brian West (bkw918) 2003-09-28 23:02:20|
"Yuck! Error in buffer handling" not related. And mine works fine... Sounds liek a codec issue.
By: master (master) 2003-09-29 22:12:32
To roll back only the affected stuff for SIP negotiation, I would
cvs update -j 1.181 -j 1.179 channels/chan_sip.c
Note that the second line should only be executed *once*. Once this is fixed in CVS, you should *remove* channels/chan_sip.c to make sure the changes done by the second line above are removed again.
By: Brian West (bkw918) 2003-09-29 22:13:59
If you are using nat... then change nat=1 to nat=yes thats what was broken. I don't use nat so I cant tell its broken.
By: Brian West (bkw918) 2003-09-30 14:27:35
is this still an issue?
By: Mark Spencer (markster) 2003-09-30 22:51:58
This was broken in CVS. Believe it's fixed now.
By: John Todd (jtodd) 2003-09-30 22:53:32
Mark believes (as do I) that this was fixed with changes to chan_sip earlier yesterday/today. Marking as "resolved" - please complain if this is not the case.