search for: borot

Displaying 5 results from an estimated 5 matches for "borot".

Did you mean: boot
2005 Mar 15
9
Asterisk Newbie
Hello all I have been learning * from almost 1 month now. It looks really powerfull. I have some problem trying to find previous post, or solutions to common problems, advice to newbies etc in this mailing list. There is no a forum-like tool to search thru the posts by keyworks for example. Please correct me if I am wrong. That is why I will post my questions here: 1- Transcoding: is this when
2023 Jan 31
1
set codec based on B side
Using Asterisk 18.12.0, a little confused on how to configure my pjsip.conf file to determine the codec to use for a call I have 2 endpoints: [Alice] disallow:all allow:ulaw,alaw,g729 [Bob] disallow:all allow:ulaw,alaw,g729 Alice calls into Asterisk on ext 100 and then we dial Bob I want to wait until Bod side codec is chosen to answer Alice and have each channel use the codec chose on Bob
2015 Feb 23
2
Question about Warning message
Starting with Asterisk 13.1 we are seeing this WARNING messages a lot in our logs and console: WARNING[25164][C-0004865e]: chan_sip.c:7364 sip_write: Can't send 10 type frames with SIP write) We found that line in function "sip_write" inside "chan_sip.c". In our previous version (11.2.1) we did not see those messages being printed (same verbosity level). We compared
2015 Feb 27
0
Reply to INVITE with 1 codec
In Version 1.8 asterisk introduced this parameter preferred_codec_only, when set to "yes" the 200 OK to the INVITE contains 1 codec only from the available ones in the user sip profile. But in version 13.1 (I think version 11.2 also) is not working like that , it keeps sending all the codecs and sometimes both parties pick a different one causing one way audio. Example: INVITE has ulaw,
2015 Mar 05
0
Asterisk removes SDP from 180 with SDP
Asterisk receives a 180 Ringing with SDP from the called side, then it sends 180 without SDP to the calling side. We would like asterisk to sends to the calling side the same response that was received from the called side. This is Asterisk cert 13.1, is that a new behavior, is there a setting to change this ? ?