Hi,
Working with CNXCC for quite some time now with success. Though running
into the following problem. Running Kamailio 4.4 (Debian Wheezy) from
the Kamailio repository.
Setting up CNXCC with a dialog start event route, a dialog end event
route and a cnxcc:shutdown event route. In the start even
Yasin,
1. The Request URI of the ACK must match the Contact of the other end
(the Contact URI in the 200 OK), was you correctly surmised. This
includes all attributes of the Contact URI, including port.
2. The ACK you pasted needs to contain Route: headers whose values match
the Record-Route
Hello;
before sending this email i searched on google and doesnt solve
this issue. all call flows are correct but one call that this isnt
working right. it sends to wrong port to ACK for 200 OK. i
tried to fix contact header or remove contact header but it wasnt
w
Hi,
>>On 06/04/16 01:57, Marrold wrote:
>> Hi Charles,
>>
>> I can confirm that t_any_timeout(), and t_branch_timeout() return true
>> when these un-ACKd transactions occur.
> by un-ACKed, do you mean they didn't receive any response or they didn't
> receive the ACK following a response to an INV
Hello,
based on some of the plans for Kamailio 5.0
(https://www.kamailio.org/wiki/devel/kamailio-5.0-design), I started the
implementation for the support to allow writing the active routing logic
at runtime (respectively what are now the routing blocks) in other
embedded languages than the native
I personally am against this 'version' table concept altogether. It just makes
life difficult for expert users without meaningfully solving the problem it
seeks to solve.
It's just an arbitrary table; what guarantees does it offer that the version of
the definition of table X corresponds to t
Alex Lutay writes:
> The point here that Kamailio checks DB table_version and doesn't start
> if the version mismatch found.
Yes, it makes sense to be able to run older version of k on newer table
versions as long as newer versions of tables are backwards compatible,
e.g., a new field has been ad
Hi,
We are heavily using Kamailio in our product Sipwise NGCP and currently
testing possibility to provide rollback for the customers with the huge
systems as the last resort functionality in case if upgrade went wrong.
We hope never use it on practice but prefer to have such possibility.
The mai
