[asterisk-dev] Fwd: res_pktccops

Mon Jan 4 09:27:20 CST 2010

It's a subset or a "profile" of the IETF COPS protocol, extended for
PacketCable specific usage. The IETF COPS RFC defines the extensions
mechanism and the PacketCable standard uses and respects them. For
example, IETF COPS defines an opaque field called "Client Specific
Decision Data" and the PacketCable Standard defines how to fill it.
Some IETF COPS messages are not used in the PC Standard (like SSC), so
is a subset.

This standard is used only in conjunction with NCS, so is safe to
disable res_pktcops if chan_mgcp is not active. But if you use
chan_mgcp with NCS peers, is 99% certain you need to configure and use
res_pktcops.

There is posterior COPS based standard called PacketCable MultiMedia,
used to allocate bandwidth for SIP/(whatever VoIP) calls, but
res_pktcops doesn't knows about it.

Here is the documentation for the res_pktccops.conf sample file:

--------------------------------------
[general]
;; Polling interval to get gate information from the CMTS's (gate ==
allocated bandwidth for an IP)
gateinfoperiod => 60 ; default 60s

;; Time to assume the gate is closed if there is no response for the
gate information request
gatetimeout = 150 ; default 150

;; Various COPS timers, no need to change them
t1 => 250 ; default 250s
t7 => 200 ; default 200s
t8 => 300 ; default 300s

;; Interval between COPS connection KeepAlive messages, to know the CMTS are up
keepalive => 60 ; default 60s

;; CMTS's definitions

; At start, res_pktcops establishes a COPS connection for each one of the CMTS's
; When chan_mgcp ask for bandwidth allocation for a call, res_pktcops uses an
; established COPS connection to ask the CMTS having the
originating/terminating IP
; in their pool to allocate a "gate" (QoS reservations) for that call.

[myfirstcmts]
; CMTS IP to connect to (one connection per CMTS)
host => 192.168.0.24

; IP Networks managed by the CMTS (to allocate bandwidth for)
; pool => network [space] mask
pool => 10.0.1.0 10.0.1.255
pool => 10.0.3.0 10.0.3.255
pool => 10.0.7.0 10.0.8.255
pool => 10.0.10.0 10.0.11.255

--------------------------------------

Saludos,
Nahuel Greco.

On Mon, Jan 4, 2010 at 4:31 AM, Olle E. Johansson <oej at edvina.net> wrote:
>
> 4 jan 2010 kl. 00.17 skrev Nahuel Greco:
>
>> Maybe you missed this answer from me?:
>>
>> --
>> This module was added in a chan_mgcp patch, to add support for the
>> PacketCable MGCP variation called NCS. Res_pktccops implements COPS
>> (RFC 2748), a protocol used to manage dynamic bandwith allocation in
>> CMTS's (HFC gateways). When you use NCS, you need to talk COPS with
>> the CMTS to complete the calls, so I think the sane default is to
>> enable res_pktcops if chan_mgcp is enabled.
>
> Yes, I missed it. Sorry, but thanks for repeating it.
>
>>
>> The PacketCable consortium extends IETF COPS to define a protocol used
>> to ask CMTS's allocate bandwidth for calls.
>>
> Did they change the IETF protocol or is this just an implementation of the IETF protocol?
>
> /O
>>
>> Saludos,
>> Nahuel Greco.
>>
>>
>>
>> On Sun, Jan 3, 2010 at 7:44 AM, Olle E. Johansson <oej at edvina.net> wrote:
>>> I sent this in november and must have missed any answers. I vote for disabling this module as enabled by default in menuselect until we have a module that can be properly disabled in configuration and have some documentation on what it really is.
>>>
>>> Is this the IETF COPS protocol or a proprietary version of COPS from the PacketCable consortium?
>>>
>>> Does anyone of the developers understand what we have included in Asterisk?
>>>
>>> /O
>>>
>>> Vidarebefordrat brev:
>>>
>>>> Från: "Olle E. Johansson" <oej at edvina.net>
>>>> Datum: 4 november 2009 09.15.06 CET
>>>> Till: Asterisk Mailing List Developers <asterisk-dev at lists.digium.com>
>>>> Dold kopia: "Olle E. Johansson" <oej at edvina.net>
>>>> Ämne: res_pktccops
>>>>
>>>> This module has almost no documentation - what does it do?
>>>> Any external references to protocols?
>>>>
>>>> The sample config seems to enable a lot of stuff - which other module configurations tries to avoid. Many additional modules that implement special protocols are disabled by default - this module is enabled and configured by default.
>>>>
>>>> I think we need at least some basic level of documentation to accept modules like this. The only thing I find is this doxygen:
>>>>
>>>> /*!\file
>>>> *
>>>> * \brief PacketCable COPS
>>>> *
>>>>
>>>> That's far from enough.
>>>>
>>>> Regards,
>>>> /O
>>>
>>>
>>> _______________________________________________
>>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>>
>>> asterisk-dev mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>>
>>
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> ---
> * Olle E Johansson - oej at edvina.net
> * Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
>
>
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>