Displaying 5 results from an estimated 5 matches for "a611e".
Did you mean:
611e
2008 Aug 05
0
When shall SIP phone reply "480 Temporarily Unavailable"
...with
:
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK690b7694;rport
From: "9121 Guest1"<sip:9121 at 192.168.100.254 <sip%3A9121 at 192.168.100.254>
>;tag=as237a9159
To: <sip:9121 at 192.168.100.198:5060;user=phone>;tag=c0a80101-a611e
Call-ID: 6bddeb200c2aee553856dab4098c6f8e at 192.168.100.254
CSeq: 102 INVITE
Content-Length: 0
Is it normal to reply this way ?
I tried with another SIP phone (a Siemens Gigaset) and it accepted the
INVITE (and started to ring).
regards
-------------- next part --------------
An HTML attachme...
2008 Aug 01
1
Comparing origination from CLI and from AMI
Hi,
Using FOP, I've met a situation which makes me ask this simple question :
Are both A and B commands bellow equivalent ?
A. CLI:
originate SIP/9122 application dial Local/9123 at local
B. AMI/FOP:
192.168.64.5 -> Action: Originate
192.168.64.5 -> Channel: SIP/9122
192.168.64.5 -> Async: True
192.168.64.5 -> Callerid: 9122 Guest2 <9122>
192.168.64.5 -> Exten: 9123
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
Hi Karthik,
thanks for taking a look at this. I'm not working with gluster long
enough to make heads or tails out of the logs. The logs are attached to
this mail and here is the other information:
# gluster volume info home
Volume Name: home
Type: Replicate
Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a
Status: Started
Snapshot Count: 1
Number of Bricks: 1 x 3 = 3
Transport-type: tcp