Earlier I was using asterisk 1.4 and 1.6. In these version it used to
do native bridging and the CPU load was not very high. Now after
switching to asterisk 1.8 it has started to do remote bridging and the
CPU load has often started to peak.
Could this be a configuration issue. I have done the same SIP settings
that was earlier there in 1.4 and 1.6. I have ‘directmedia=yes’ and
‘directrtpsetup=yes’ in sip.conf and both the peers use the same
codecs and there are no nat issues as well
On Thu, Mar 29, 2012 at 7:29 PM, Phil Frost
> On Mar 29, 2012, at 08:43 , Deepesh D wrote:
>> What are the different type of bridging used by asterisk in a SIP
>> call? What is the difference between Packet2Packet bridging, Remote
>> bridging and Native bridging?
> Packet2Packet bridging is when RTP datagrams are forwarded by Asterisk without modification. This imposes little load on the CPU. Obviously this can only happen if both ends are using the same codec, and likely there are likely other less obvious conditions that must be met.
> Remote bridging happens when Asterisk can direct both ends to send media (RTP probably) to each other directly, by a SIP reINVITE, for example. Only works if both ends have a route to each other, Asterisk is configured to do it, each end shares a codec, and probably a dozen other more subtle conditions are true. In this case there is no load on Asterisk as it’s not even in the media path. It also means it can’t do things like intercept and act on DTMF or monitor the call.
> Native bridging is when media is forwarded with Asterisk, but for whatever reason (different codecs, maybe) Asterisk must inspect or modify the stream. Could mean a significant CPU load.
> Phil Frost
> office 248-893-0738
> direct 248-662-0809
> — Bandwidth and Colocation Provided by http://www.api-digital.com –
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit: