Zulu not connecting when calling specific numbers

Commercial Modules Zulu
1

Here’s an example. If I call this number 8579571130 (start meeting) with my Zulu app it just says “connecting” and never does anything else. I can call any other 10 digit number or extension just fine. In fact none of my zulu users can call that number. The same thing happens for everyone.

If I call that same number using my cell phone or my sangoma phone (same extension as zulu) it works just fine.

Here’s the log for that call grepped out of “full”.

[[email protected] asterisk]# tail -f full | grep -i "8579571130"
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:1] Macro("PJSIP/9077228-00000401", "user-callerid,LIMIT,EXTERNAL,") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:2] Gosub("PJSIP/9077228-00000401", "sub-record-check,s,1(out,8579571130,dontcare)") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:1] NoOp("PJSIP/9077228-00000401", "Outbound Recording Check from 77228 to 8579571130") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:7] Gosub("PJSIP/9077228-00000401", "recordcheck,1(dontcare,out,8579571130)") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:3] ExecIf("PJSIP/9077228-00000401", "0 ?Set(CDR(accountcode)=)") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:4] Set("PJSIP/9077228-00000401", "MOHCLASS=default") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:5] Set("PJSIP/9077228-00000401", "_NODEST=") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:6] Macro("PJSIP/9077228-00000401", "dialout-trunk,1,18579571130,,off") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:2] UserEvent("PJSIP/9077228-00000401", "zulu-outbound-call,from:77228,to:18579571130") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:7] Set("PJSIP/9077228-00000401", "DIAL_NUMBER=18579571130") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:16] Set("PJSIP/9077228-00000401", "OUTNUM=+18579571130") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:22] ExecIf("PJSIP/9077228-00000401", "1?Set(CONNECTEDLINE(num,i)=18579571130)") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] pbx.c: Executing [[email protected]:27] Dial("PJSIP/9077228-00000401", "SIP/BW-SIP-A/+18579571130,300,Tb(func-apply-sipheaders^s^1,(1))") in new stack
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] app_stack.c: Spawn extension (from-trunk, 8579571130, 1) exited non-zero on 'SIP/BW-SIP-A-000006ca'
[2020-02-18 10:54:14] VERBOSE[3354][C-00000431] app_dial.c: Called SIP/BW-SIP-A/+18579571130
[2020-02-18 10:54:15] VERBOSE[3354][C-00000431] pbx.c: Spawn extension (from-internal, 8579571130, 6) exited non-zero on 'PJSIP/9077228-00000401'
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:1] Macro("PJSIP/73004-00000410", "user-callerid,LIMIT,EXTERNAL,") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:2] Gosub("PJSIP/73004-00000410", "sub-record-check,s,1(out,8579571130,dontcare)") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]ecord-check:1] NoOp("PJSIP/73004-00000410", "Outbound Recording Check from 73004 to 8579571130") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:7] Gosub("PJSIP/73004-00000410", "recordcheck,1(dontcare,out,8579571130)") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:3] ExecIf("PJSIP/73004-00000410", "0 ?Set(CDR(accountcode)=)") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:4] Set("PJSIP/73004-00000410", "MOHCLASS=default") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:5] Set("PJSIP/73004-00000410", "_NODEST=") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:6] Macro("PJSIP/73004-00000410", "dialout-trunk,1,18579571130,,off") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:2] UserEvent("PJSIP/73004-00000410", "zulu-outbound-call,from:73004,to:18579571130") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:7] Set("PJSIP/73004-00000410", "DIAL_NUMBER=18579571130") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:16] Set("PJSIP/73004-00000410", "OUTNUM=+18579571130") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:22] ExecIf("PJSIP/73004-00000410", "1?Set(CONNECTEDLINE(num,i)=18579571130)") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] pbx.c: Executing [[email protected]:27] Dial("PJSIP/73004-00000410", "SIP/BW-SIP-A/+18579571130,300,Tb(func-apply-sipheaders^s^1,(1))") in new stack
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] app_stack.c: Spawn extension (from-trunk, 8579571130, 1) exited non-zero on 'SIP/BW-SIP-A-000006ee'
[2020-02-18 10:56:12] VERBOSE[6040][C-00000449] app_dial.c: Called SIP/BW-SIP-A/+18579571130
2

The number is being dialed out your trunk, but it’s not terminating. This is not a Zulu or PBX issue.

3

The weird thing is I can dial that number just fine using my sangoma phone connected to the same PBX. I can dial the number using my cell phone too. It’s only when we try to call that number using Zulu that it never connects. Duplicated the issue 3 times with different Zulu users.

I believe you Lorne I’m just trying to figure out why we can’t call startmeeting numbers with Zulu. All the numbers that don’t work are startmeeting numbers.

4

Maybe startmeeting is rejecting the zulu call for some reason. I’ll reach out to them.

5

Could it be caller ID related or something?

1 Like
6

I was thinking the same thing. I don’t see anything off in the CID for these zulu extensions.

7

At the Asterisk command prompt type
sip set debug on
and make two test calls, a failing call from Zulu and a successful one from a Sangoma phone.
Paste the logs at https://pastebin.freepbx.org and post the link here.

8

This PBX has over 500 extensions. Is there a way to see the debug for just the test calls? When I turn on the debug the screen goes crazy with information.

9

sngrep

10

You could do
sip set debug peer BW-SIP-A
to see only calls on that trunk. After giving the command, quit out of the Asterisk console, make your test calls, reconnect to Asterisk and type
sip set debug off

11

In the log you originally posted, the steps between [[email protected]:7] and [[email protected]:16] should have been setting up the caller ID. You can compare those values for working and failing calls.

12

They look the same (except the nonworking shows my extension as 9077228 instead of 77228). Other than that the log looks identical. Still trying to get a sip debug log for ya.

13

That’s strange. Neither of those are valid caller IDs. On a normal call from an extension to your mobile, is the Outbound CID set for your extension displayed on the mobile? If not, are you forcing a CID in the Outbound Route or Trunk settings? Or does your trunk configuration or settings at your provider (Bandwidth?) override the CID from the PBX?

14

I see my caller ID on my cell when I call it from Zulu and it looks right. It’s showing what I have in the outbound CID field in the extension on freepbx

15

Non working Zulu test call:

https://pastebin.freepbx.org/view/948715d0

Working desk phone test call:

https://pastebin.freepbx.org/view/e957fcde

Both tests were done by calling 8579571130 from extension 77228

16

Oddly enough I downgraded to Asterisk 13 last night and now the zulu calls go through to startmeeting. I had to downgrade because this system has become so unstable that I figured I’d roll back to the version of Asterisk where we had the least amount of problems.

17

Okay this is not fully resolved. It looks like we’ve narrowed down the issue to when Zulu makes outbound calls to any number that has an automated answer.

18

We’ve pretty much moved most of our entire company to soft phones while they work from home during this national emergency. I’ve had multiple reports that Zulu users cannot call in to startmeeting. They get a fast busy. When they try with their cell phones it connects just fine. I’m at a loss here.