GV Connects but doesn’t take inbound or outbound calls

Devon Betts

New Member
Joined
Oct 2, 2018
Messages
5
Reaction score
0
Hey everyone, I’m using the latest addition of Incredible PBX and I I’ve got GV connected and all set up but for some reason when I place a call it rings endlessly (without actually calling anyone) and incoming calls just never come in. If anyone can help with this I would appreciate it.
 
Joined
Sep 23, 2017
Messages
98
Reaction score
22
I had an issue as well. The GVSIP trunks would connect then I could make one call to them if I did it as soon as they connected. A few minutes later they did not ring into the system. I could do a amportal restart or fwconsole restart and they would come online for a few minutes then stop working. I could not get more than one call to them. The next day when I checked the trunks in "Reports\Asterisk Info\Chan_PJSip Info" I saw the wording "Rejected" on my trunks. I deleted both GVSIP trunks and added them back in and they did the same thing. Rings once and the next day rejected.

I found this thread

https://pbxinaflash.com/community/t...erisk-13-23-0-seems-to-fix-the-problem.23083/

Post 13 gives instructions on how to upgrade to 13.23.0 as the current version. When I ran the command I got 13.23.1 as the current version. I ran the whole upgrade and it has been running fine since.

As a caution when running any upgrade backup your system before you start. Since this is on a raspberry pi (same as mine) just make an image of your sd card. That way if your upgrade goes egg shaped you can go backwards.
 

Devon Betts

New Member
Joined
Oct 2, 2018
Messages
5
Reaction score
0
I had an issue as well. The GVSIP trunks would connect then I could make one call to them if I did it as soon as they connected. A few minutes later they did not ring into the system. I could do a amportal restart or fwconsole restart and they would come online for a few minutes then stop working. I could not get more than one call to them. The next day when I checked the trunks in "Reports\Asterisk Info\Chan_PJSip Info" I saw the wording "Rejected" on my trunks. I deleted both GVSIP trunks and added them back in and they did the same thing. Rings once and the next day rejected.

I found this thread

https://pbxinaflash.com/community/t...erisk-13-23-0-seems-to-fix-the-problem.23083/

Post 13 gives instructions on how to upgrade to 13.23.0 as the current version. When I ran the command I got 13.23.1 as the current version. I ran the whole upgrade and it has been running fine since.

As a caution when running any upgrade backup your system before you start. Since this is on a raspberry pi (same as mine) just make an image of your sd card. That way if your upgrade goes egg shaped you can go backwards.
Thanks for the reply, I found out that I was not running the latest version, I was running the older version from 2017 and I also, found out I wasn't using GVSIP I was using the old Motif which did connect but like I said, never worked. I updated to the latest version on my Pi 3 using the new GVSIP and now all seems to be up and running!
 

Devon Betts

New Member
Joined
Oct 2, 2018
Messages
5
Reaction score
0
So now I'm having the issue were GV doesn't connect to they system and the server just keeps saying the same error message "The Number is not answering" It just stopped working out of the blue. Didn't restart the server or anything. I ended reinstalling everything and still the same error

[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s@macro-dialout-trunk:32] NoOp("SIP/98-00000004", "Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 18") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s@macro-dialout-trunk:33] GotoIf("SIP/98-00000004", "0?continue,1:s-CHANUNAVAIL,1") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx_builtins.c: Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] Set("SIP/98-00000004", "RC=18") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s-CHANUNAVAIL@macro-dialout-trunk:2] Goto("SIP/98-00000004", "18,1") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx_builtins.c: Goto (macro-dialout-trunk,18,1)
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [18@macro-dialout-trunk:1] Goto("SIP/98-00000004", "s-NOANSWER,1") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx_builtins.c: Goto (macro-dialout-trunk,s-NOANSWER,1)
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:1] NoOp("SIP/98-00000004", "Dial failed due to trunk reporting NOANSWER - giving up") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:2] Progress("SIP/98-00000004", "") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:3] Playback("SIP/98-00000004", "number-not-answering,noanswer") in new stack
[2018-10-15 21:15:03] VERBOSE[11934][C-00000004] file.c: <SIP/98-00000004> Playing 'number-not-answering.ulaw' (language 'en')
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:4] Congestion("SIP/98-00000004", "20") in new stack
[2018-10-15 21:15:05] WARNING[11934][C-00000004] channel.c: Prodding channel 'SIP/98-00000004' failed
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] app_macro.c: Spawn extension (macro-dialout-trunk, s-NOANSWER, 4) exited non-zero on 'SIP/98-00000004' in macro 'dialout-trunk'
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Spawn extension (from-internal, 96083465489, 5) exited non-zero on 'SIP/98-00000004'
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Executing [h@from-internal:1] Macro("SIP/98-00000004", "hangupcall") in new stack
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Executing [s@macro-hangupcall:1] GotoIf("SIP/98-00000004", "1?theend") in new stack
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Executing [s@macro-hangupcall:3] ExecIf("SIP/98-00000004", "0?Set(CDR(recordingfile)=)") in new stack
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Executing [s@macro-hangupcall:4] Hangup("SIP/98-00000004", "") in new stack
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] app_macro.c: Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'SIP/98-00000004' in macro 'hangupcall'
[2018-10-15 21:15:05] VERBOSE[11934][C-00000004] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/98-00000004'
 

Members online

Forum statistics

Threads
25,821
Messages
167,814
Members
19,246
Latest member
abuhyder
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top