Matthew Fredrickson wrote: > 2.) A new channel driver, called chan_ccs, that allows, among other > things, you to control MGCP media gateways for bearer trunks, instead of > having to locally terminate them on the asterisk box that's controlling > the signalling links. There is also code in the same branch that has > chan_ccs that modified chan_mgcp so that Asterisk can act as a media > gateway (since I don't have any good real media gateways to test on). > This basically means you can have Asterisk TDM channel scalability up to > (in the ideal state) the same level as you can do with SIP with no > media, per box. > > In essence, this is turning Asterisk into a "true" softswitch, allowing > native bridging between media gateways and any other RTP endpoint > (including other media gateways). This also means that you don't have > to terminate bearer T1s/E1s on the main signalling box. Hi Matthew! This is an interesting new feature. I wonder if following features are also supported, or at least planned to be supported? e.g. - rtp timeout: if MGW detect rtp timeout, MGWC should send BYE - T.38 reINVITE: if MGW detects a fax, MGWC should initiate reINVITE to T.38 ... regards Klaus
|