Provide a log of a failed call, make sure you get as much from the wiki as you can.
↧
"architecture" of the call?
↧
WebPhone don't connect
When I give Firefox permission to access the microphone, it automatically drops and displays this:
== Setting global variable ‘SIPDOMAIN’ to ‘xxxx.xxxx.xxx.xx’
It authenticates but can not make calls. Any idea?
↧
↧
External calls not making it through
Hi all!
Wondering if anybody has any other ideas or things I can try? I’m still able to dial outside lines. But when users attempt to dial in, they hear silence and the call eventually fails.
One update; San Diego CA recently made a change where callers need to dial 1+area code+number, even for local calls. My incoming routes are currently set for 10-digit dialing (without the 1). I added the 1 for one of my extensions, but same result. So I don’t think that change led to my current problem, but thought I’d mention just in case.
Thanks again!
↧
Anonymous queue calls get incorrect prefix
Hello,
I have a similar issue to this one from 2008: https://community.freepbx.org/t/cid-name-prefix-lost-for-anonymous-callers/3657/5
I have several queues setup and calls with a caller ID of anonymous get assigned one specific prefix, regardless of which queue it really come sin on. What is sort of odd is that the CDR shows the correct queue prefix; it is just on the phone’s screen that the incorrect prefix shows up.
Phone in question is an Aastra (Mitel) 6869i.
I don’t know if this is just something stupid in the way Aastra handles anonymous CIDs, or if something isn’t being passed to the phone properly by FreePBX.
Versions I have are:
FreePBX: 10.13.66-22
Core: 13.0.122.33 (just recently updated; not sure if this was an issue before the update)
One thing I will do is to see if I can replicate this on a test system with the same phone my client has. Once i do, I will swap my phone with a Sangoma and see if the issue persists and report back. That should at least identify if it is an Aastra/Mitel issue or something to do with FreePBX.
(Obviously if it is an Aastra/Mitel issue, I strongly suspect there isn’t much, if anything, that could be done on the FreePBX side; it’s something I would have to take up with them?)
I will report back shortly.
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
When you get the asterisk source files, there a shell script included:-
contrib/scripts/install_prereq
It conveniently looks for the software A) that is necessary and B) that the ‘addons’ like to have. It is OS independent and will in this case, have suggested and then by request have the appropriate package manager install all the above.
If you regularly “roll-your-own” you will have long ago have realized that it might well save hours later in the ./configure/make/make install/make config/test_if_you_got_what_you_want cycle.
Edit : After reviewing the install process, you found the mp3 script in that directory but you REALLY don’t want to do “make samples” thing on a working FreePBX 
( the other scripts in that directory are also worth looking at 
)
↧
↧
Anonymous queue calls get incorrect prefix
I made a call to my test queue on my client’s system, and my anonymous call came through with the correct prefix. The phone I was testing from is a 6867i whereas my clients phone at Reception is a 6869i, and I don’t have access to one of those.
Firmware on the 6869i is 4.1.0.3013 but latest version available (as supplied by Endpoint Manager) is 4.2.0.2023. I am going to see if upgrading the firmware will resolve the issue.
I will test with the client tomorrow morning and update with results.
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
@dicko I am assuming that means on a fresh install, meaning the first time setting it up after install ubuntu, it would be ok to do the “make samples” then.
But when you build again the latest changes, you should NOT be running that command? I assume it would wipe out some of the changes you made if you did.
Thanks, and if I am assuming this correctly. I will make note of it in the opening post.
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
It would probably be ‘ok’ but it would be a waste of time if two lines later you install FreePBX, from that point onwards, modifying anything that is not a “custom” or “override” file will not be “a good thing”, Just delete that ‘unnecessary’ from your process and you will be fine.
↧
GV Trunk Issue Diagnosis
Thank you - and facepalming myself for not realizing this is all a downstream effect of the GV XMPP termination.
Following all relevant threads now and will likely settle with an Obi200 providing the GV trunks and then onward to FreePBX for the immediate future.
↧
↧
Yum Update errors following upgrade to SNG7
Did you ever get a fix for this problem?
I upgraded a server today and have the same issue.
↧
Update 10.13.66-22 to 12.7.5-1805-3.sng7 yum update errors
Today I updated a 10.13.66-22 server to 12.7.5-1805-3.sng7. All appeared ok, but when I logged in, I received the message “There are 323 System updates available. Run yum update to update them.”
I ran yum update and received the following messages, the staff will be back in the morning and I would really like to solve this before they arrive!
Transaction Summary
Install 6 Packages (+38 Dependent packages)
Upgrade 313 Packages
Total size: 434 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/share/syslinux/cat.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/chain.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/cmd.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/config.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/cpuid.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/cpuidtest.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/disk.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/dmitest.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/elf.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/ethersel.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/gfxboot.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/gpxecmd.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/gpxelinux.0 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/gpxelinuxk.0 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/hdt.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/host.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/ifcpu.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/ifcpu64.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/ifplop.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdpfx.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdpfx_c.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdpfx_f.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdppx.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdppx_c.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isohdppx_f.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isolinux-debug.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/isolinux.bin from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/kbdmap.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/linux.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/ls.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/lua.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/mboot.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/memdisk from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/memdump.com from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/meminfo.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/menu.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/pcitest.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/pmload.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/pwd.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/pxelinux.0 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/reboot.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/rosh.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/sanboot.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/sdi.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/sysdump.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/syslinux.com from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/syslinux.exe from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/syslinux64.exe from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/vesainfo.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/vesamenu.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/vpdtest.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
file /usr/share/syslinux/whichsys.c32 from install of syslinux-4.05-13.el7.x86_64 conflicts with file from package syslinux-nonlinux-4.04-3.el6.noarch
↧
Update 10.13.66-22 to 12.7.5-1805-3.sng7 yum update errors
Try running the repair script at the bottom of this page:
https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7#UpgradingfromFreePBX10.13.66toSNG7-Recoveryfromafailedupgrade
↧
Update 10.13.66-22 to 12.7.5-1805-3.sng7 yum update errors
Sorry, forgot to include that I did run the repair.
I ran the repair a second time, it did not fix the problem.
Still looking for an answer!
↧
↧
FreePBX 12 - video calls & G722
Thank you Pitzkey,i will try then.
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
I’ve followed the asterisk rebuild process presented for IncrediblePBX from page 26267 of the nerdvittles site (can’t post the link).
Everything compiles without error, but I don’t have a working system. If anybody can explain why I can’t place an outgoing call, I’d appreciated it:
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
> 0xb6324220 – Strict RTP learning after remote address set to: 192.168.2.21:5004
– Executing [6085------@from-internal:1] Set(“SIP/1024-00000003”, “CALLERID(dnid)=6085------”) in new stack
– Executing [6085------@from-internal:2] Set(“SIP/1024-00000003”, “CALLERID(dnid)=16085------”) in new stack
– Executing [6085------7@from-internal:3] Goto(“SIP/1024-00000003”, “16085------,1”) in new stack
– Goto (from-internal,16085------,1)
– Executing [16085------@from-internal:1] Set(“SIP/1024-00000003”, “CHANNEL(accountcode)=Google Voice”) in new stack
– Executing [1608------@from-internal:2] Dial(“SIP/1024-00000003”, “PJSIP/16085------@gvsip,r”) in new stack
[2018-07-04 18:53:17] ERROR[3286]: chan_pjsip.c:2215 request: Unable to create PJSIP channel - endpoint ‘gvsip’ was not found
[2018-07-04 18:53:17] WARNING[3285][C-00000002]: app_dial.c:2527 dial_exec_full: Unable to create channel of type ‘PJSIP’ (cause 3 - No route to destination)
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [16085------@from-internal:3] Progress(“SIP/1024-00000003”, “”) in new stack
– Executing [16085------@from-internal:4] Wait(“SIP/1024-00000003”, “1”) in new stack
> 0xb6324220 – Strict RTP switching to RTP target address 192.168.2.21:5004 as source
– Executing [16085------@from-internal:5] Playback(“SIP/1024-00000003”, “silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer”) in new stack
– Playing ‘silence/1.ulaw’ (language ‘en’)
– Playing ‘cannot-complete-as-dialed.ulaw’ (language ‘en’)
– Playing ‘check-number-dial-again.ulaw’ (language ‘en’)
↧
GV Trunk Issue Diagnosis
I do not recommend buying anything else from Obihai, as it simply encourages them to keep obsoleting current models and introducing new ones in future money grabs. You are free to do what you like, but I think one of the reasons some people are working so hard on this problem is because they resent the way Obihai apparently regards their customers as nothing more than open wallets to be shaken every few years. If you have a current Obihai model, or any other VoIP device that supports the SIP protocol, that is all you need to connect to FreePBX. I do understand that these are uncertain times in that we don’t yet know what will turn out to be the best way to continue connecting with Google Voice on an ongoing basis, but my bet would be that a solution involving FreePBX and Asterisk will ultimately last longer than any Obihai device you might purchase.
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
Sorry its been about 7 years since ive tried IncrediblePBX, you might try asking over here: https://pbxinaflash.com/community/forums/
When I first started using google voice I used IncrediblePBX for about a year or two. Then I had an issue, its been so long I can’t even remember what it was, I actually think it might have been when I switched from using pygooglevoice to GV motif, so I installed Freepbx distro, and I ran that for about the last 6 years without really any problems.
To just readover what you posted, one line seems to indicate that the ‘gvsip’ trunk is missing, however without having tried IncrediblePBX recently, I could not speculate why.
↧
↧
Implementing and Testing Naf's GVsip Google Voice Sip Ubuntu 18.04 Freepbx
One could also modify the Google voice module to add everything that’s needed in here. Including adding the additional settings into pjsip. Only issue is being able to tell if it’s nafs version of asterisk.
↧
Zulu Desktop Screen Sharing
It’s in experimental features under settings in the Zulu client.
↧
Strange extension numbers.. 99xxx and 9999xxx
Just call the regular extension
↧