[asterisk-r2] Protocol error. Reason = Seize Timeout - Openr2

[Moises Silva]

On Wed, Jul 8, 2009 at 9:10 AM, Melcon Moraes <melcon at gmail.com> wrote:

> The difference is how the call is supposed to be billed/processed by the
> far end. You can accept or reject calls according to its category.
>
> I think that most of the available categories are not used anymore, just a
> few ones, depending on the country practices.
>
> This is MF signaling, not CAS. The seize timeout is CAS related and happens
> way before the category exchange.


As Melcon pointed out, that parameter does not affect the seize behavior and
no, there is nothing you can do from a configuration point of view, in terms
of tcp connections is like doing "telnet telco.host.com" and after a few
seconds getting connection timed out. What can you do from telnet
prespective? nothing, the problem is either in the network (your cabling) or
the far end.

-- 
Moises Silva
Software Developer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090708/e220f980/attachment.htm