Displaying 5 results from an estimated 5 matches for "43e4".
Did you mean:
434
2020 Feb 04
2
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...1]: bridge.c:809
bridge_base_init: Bridge da3bd3d1-cdea-4a05-8b3d-0ded8c561c5f: Could not
initialize topics
Asterisk 13
[2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c: Bridge
id initialization required
[2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
0e8746e2-43e4-4c7c-9df8-32d7fe6e3727: Could not initialize topics
Switching back to previous versions and problem disappear
--
Daniel
2020 Feb 04
0
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...Bridge da3bd3d1-cdea-4a05-8b3d-0ded8c561c5f: Could not
> initialize topics
>
> Asterisk 13
>
> [2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c: Bridge
> id initialization required
> [2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
> 0e8746e2-43e4-4c7c-9df8-32d7fe6e3727: Could not initialize topics
>
> Switching back to previous versions and problem disappear
>
Please file an issue on the issue tracker[1] with complete console output
and dialplan if possible. This isn't something that has been seen in
testing and there hasn'...
2020 Feb 04
1
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...5f:
> Could not
> initialize topics
>
> Asterisk 13
>
> [2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c:
> Bridge
> id initialization required
> [2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
> 0e8746e2-43e4-4c7c-9df8-32d7fe6e3727: Could not initialize topics
>
> Switching back to previous versions and problem disappear
>
>
> Please file an issue on the issue tracker[1] with complete console
> output and dialplan if possible. This isn't something that has been
> seen in t...
2018 Jul 13
2
Upgrade to 4.1.1 geo-replication does not work
Hi Kotresh,
Yes, all nodes have the same version 4.1.1 both master and slave.
All glusterd are crashing on the master side.
Will send logs tonight.
Thanks,
Marcus
################
Marcus Peders?n
Systemadministrator
Interbull Centre
################
Sent from my phone
################
Den 13 juli 2018 11:28 skrev Kotresh Hiremath Ravishankar <khiremat at redhat.com>:
Hi Marcus,
Is the
2017 Apr 21
1
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
On 2017-04-20 18:38, Rowland Penny wrote:
> On Thu, 20 Apr 2017 18:00:24 +0200
> Sven Schwedas via samba <samba at lists.samba.org> wrote:
>
>> On 2017-04-07 13:44, Sven Schwedas via samba wrote:
>>> In the end I just upgraded all DCs to 4.5 and remote-deleted the
>>> broken ones. Seemed to work without a hitch, manual removal was
>>> only necessary