search for: b8d1

Displaying 7 results from an estimated 7 matches for "b8d1".

Did you mean: b861
2014 Dec 10
2
PJSIP configuration question
...I added the qualify_frequency as you suggested and it does appear that I have something configured incorrectly?. <--- Transmitting SIP request (483 bytes) to UDP:0.0.19.196:5060 ---> OPTIONS sip:64.2.142.93 at 5060 SIP/2.0 Via: SIP/2.0/UDP xxx.xxx.xx.xxx:5060;rport;branch=z9hG4bKPjcea63914-b8d1-483d-96db-11968abab704 From: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx>;tag=7cfab3ba-73de-4243-9967-d1e6a5e7b0b4 To: <sip:64.2.142.93 at 5060> Contact: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx:5060> Call-ID: 7ba766bf-363b-47d0-a388-62a58d1df88d...
2014 Dec 11
0
PJSIP configuration question
...SIP request (483 bytes) to UDP:0.0.19.196:5060 ---> > Well, THAT's not right. Did you obfuscate the 0.0.19.196 or is that how it really is? Are you NATed? > OPTIONS sip:64.2.142.93 at 5060 SIP/2.0 > > Via: SIP/2.0/UDP > xxx.xxx.xx.xxx:5060;rport;branch=z9hG4bKPjcea63914-b8d1-483d-96db-11968abab704 > > From: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx > >;tag=7cfab3ba-73de-4243-9967-d1e6a5e7b0b4 > > To: <sip:64.2.142.93 at 5060> > > Contact: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx:5060> > >...
2006 Jun 20
1
Caller-ID Info with Voice Mail -- Can it display to the phone?
We recently switched my wife's business over to an Asterisk setup using Cisco IP phones (7940s and 7960s) with chan_sccp. They didn't use any kind of "office-style" phone system before, they had one phone in the office with a built in answering machine that would display the Caller ID of the person who left the message while playing the message. I know in the Asterisk
2014 Dec 10
4
PJSIP configuration question
Not sure why, but Vitelity changed the settings to IP based authentication on me. Here's the new sip.conf settings they sent me. type=friend dtmfmode=auto host=64.2.142.93 allow=all nat=yes canreinvite=no trustrpid=yes sendrpid=yes When I use these settings to originate calls using the sip.conf they sent me, everything works. Action: Originate ActionID: S8 Channel:
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
...-48e3-96ca-60a988eb9358/8AFC5EBC2827D47F58F4D8D99789D0E2E1D8C8AF (aa474498-6930-41a7-8e3a-88f01ca72ae2) on home-client-2 [2017-10-25 10:14:13.059366] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/AA909E1B8D1319AFA9CC76FF0916C67EE3FBC46F (22827ea6-cb17-4001-a815-6106615096ba) on home-client-2 [2017-10-25 10:14:13.069019] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/D8A5692E5A0E83F455712F86EE389D7163DDE9CC (...