search for: rnbrady

Hi folks When connecting two SIP users, is there any way to stop Asterisk from sending SIP 183 Session Progress messages, either globally or per-peer? Call from UA1 to Asterisk (UA2) to UA3 UA3 sends RTP before SIP OK to Asterisk (UA2) Asterisk (UA2) detects early audio from UA3 and sends 183 Session Progress with SDP to UA1. Instead I would like it to just send on the early audio, is this

...has initiated a call and established the channel. The one option is to extract it from the CHANNEL variable, but that is fraught with difficulties. Is there another variable I don't know about or another way to do this? Thanks in advance! Richard -- Richard Brady T: +44 (0)7771 623 348 E: rnbrady at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081126/533032cf/attachment.htm

...expected). I would also be interested to know what the correct action is for the ITSP to take. How do they complain (using SIP and/or SDP) that the media received is not what they were expecting? Any help would be greatly appreciated. Regards, Richard -- Richard Brady T: +44 (0)7771 623 348 E: rnbrady at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081027/3f636838/attachment.htm

[Resent due to non-descriptive subject line.] Hi folks When connecting two SIP users, is there any way to stop Asterisk from sending SIP 183 Session Progress messages, either globally or per-peer? Scenario as follows: Call from UA1 to Asterisk (UA2) to UA3. UA3 sends RTP before SIP OK to Asterisk (UA2). Asterisk (UA2) detects early audio from UA3 and sends 183 Session Progress with SDP to

Hi all If Asterisk is bridging a call between two SIP peers and one peer puts the other on hold by means of a re-INVITE with SDP containing a=sendonly, Asterisk will play locally generated MOH instead of relaying the media streamed by the SIP peer which took the hold action. Any ideas how to change that? (This is understandable if the peer is a handset but can be a problem if it is a PBX with