Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 3a0bca84986d81a8d64037d082b86ae13b5a50f0
https://github.com/OpenSIPS/opensips/commit/3a0bca84986d81a8d64037d082b86ae13b5a50f0
Author: Liviu Chircu li...@opensips.org
Date: 2014-04-17 (Thu, 17 Apr
Branch: refs/heads/1.10
Home: https://github.com/OpenSIPS/opensips
Commit: 61c1481bdf10f5a280d2a1016aea392596e42ddb
https://github.com/OpenSIPS/opensips/commit/61c1481bdf10f5a280d2a1016aea392596e42ddb
Author: Liviu Chircu li...@opensips.org
Date: 2014-04-17 (Thu, 17 Apr 2014)
Branch: refs/heads/1.8
Home: https://github.com/OpenSIPS/opensips
Commit: ee2556abbce063542283b59af780721a2f01c825
https://github.com/OpenSIPS/opensips/commit/ee2556abbce063542283b59af780721a2f01c825
Author: Liviu Chircu li...@opensips.org
Date: 2014-04-17 (Thu, 17 Apr 2014)
Branch: refs/heads/1.11
Home: https://github.com/OpenSIPS/opensips
Commit: 2b2092b49a2636ac1298ea0fba086f534a31e846
https://github.com/OpenSIPS/opensips/commit/2b2092b49a2636ac1298ea0fba086f534a31e846
Author: Liviu Chircu li...@opensips.org
Date: 2014-04-17 (Thu, 17 Apr 2014)
Closed #172.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/172___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Hello,
Fixed on master, 1.11, 1.10 and 1.8.
Best regards,
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/172#issuecomment-40703023___
Devel mailing list
Devel@lists.opensips.org
Recently upgrading from 1.10 to 1.11, CDR data is no longer been generated
through an event, which then is passed to the RabbitMQ handler.
However in the startup route, I am able to successfully able to raise a
E_ACC_CDR event from the startup route.
---
Reply to this email directly or view it
I did not notice any errors in the script.
I was using latest version, both cloned and compiled today.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/207#issuecomment-40713124___
Devel mailing list
Hello,
Even though your scenario seems to work within your testing network, things
will not be the same in the real world, because the listening socket really
needs to match the initial one (of OpenSIPS instance 1) if you want to reach a
client who is behind NAT from the secondary instance
Hi, Jonathan!
Besides the heartbeat extension, nothing else has changed in the
event_rabbitmq module. Are you using this feature?
Regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 04/17/2014 04:24 PM, Jonathan Hulme wrote:
I did not notice any errors in the
I did try changing this to see if it affected behaviour. But it is disabled
after it made no difference.
If that is all that has changed in the rabbitmq then its more than likely the
bug is before the event is raised.
---
Reply to this email directly or view it on GitHub:
11 matches
Mail list logo
