Displaying 7 results from an estimated 7 matches for "b403".
Did you mean:
403
2006 Jun 05
1
This should be easy: What happens when the Calling Party hangs up
...up *before* the call is
connected to the called party. My dialplan is thus:
macro DialExternal(exten) {
Dial(Zap/G3/${exten},120,g,M(connected));
goto DialResult|r${HANGUPCAUSE}|1;
Hangup();
};
But the goto dialresult is not executed:
Executing [from-sip:1] Macro("SIP/7XX-b403", "DialExternal|xxxxxx") in
new stack
-- Executing [macro-DialExternal:1] Dial("SIP/7XX-b403",
"Zap/G3/07803034440|120|g|M(connected^jmls@mike^706)") in new stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called G3/XXXXXX
-- Zap/10-1...
2003 Jun 11
1
Busy message with call waiting?
Is it possible to have both a busy and an away message when the call
waiting feature is enabled?
extensions.conf
...
exten=>403,1,Dial,Zap/3|10
exten=>403,2,Voicemail2,u403
exten=>403,103,Voicemail2,b403
...
Because I have enabled call waiting, I can't see how it will be possible
to get the busy message to play (because there will always be a dial
tone).
Am I right, or do I have incorrect configurations?
Thanks
2020 Aug 19
4
Eaton 5E 1100i USB UPS - failed to claim USB device error
...en device,
skipping. (Permission denied) 9.901441 Checking device
(8087/0024) (002/002) 9.901448 Failed to open device,
skipping. (Permission denied) 9.901452 Checking device
(1D6B/0002) (002/001) 9.901462 Failed to open device,
skipping. (Permission denied) 9.901468 Checking device
(1B80/B403) (001/005) 9.901477 Failed to open device,
skipping. (Permission denied) 9.901483 Checking device
(18F8/0F97) (001/004) 9.901491 Failed to open device,
skipping. (Permission denied) 9.901497 Checking device
(048D/1345) (001/003) 9.901506 Failed to open device,
skipping. (Permission denied...
2020 Aug 19
0
Eaton 5E 1100i USB UPS - failed to claim USB device error
...Checking device (8087/0024) (002/002)
>
> 9.901448 Failed to open device, skipping. (Permission denied)
>
> 9.901452 Checking device (1D6B/0002) (002/001)
>
> 9.901462 Failed to open device, skipping. (Permission denied)
>
> 9.901468 Checking device (1B80/B403) (001/005)
>
> 9.901477 Failed to open device, skipping. (Permission denied)
>
> 9.901483 Checking device (18F8/0F97) (001/004)
>
> 9.901491 Failed to open device, skipping. (Permission denied)
>
> 9.901497 Checking device (048D/1345) (001/003)
>
>...
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...r_log_selfheal] 0-home-replicate-0: Completed data selfheal on bfe05b3c-a2a0-412d-9adc-51d7c1fc9ab2. sources=0 [2] sinks=1
[2017-10-25 10:40:32.037414] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on c93be6bb-58cb-4af8-b403-f17863d5fdd4
[2017-10-25 10:40:32.040719] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on c93be6bb-58cb-4af8-b403-f17863d5fdd4. sources=0 [2] sinks=1
[2017-10-25 10:40:32.053853] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr...