Some inbound callers get fast busy signal

indie
Posts: 3
Member Since:
2008-08-18

Recently some inbound callers have been getting a fast busy signal. Outbound calling is fine.

Here are the logs (redacted for privacy) from calling inbound from my cell phone and getting a fast busy:

[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [3126255599@from-pstn:1] NoOp("SIP/3126255599-09d7e608", "Catch-All DID Match - Found 3126255599 - You probably want a DID for this.") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [3126255599@from-pstn:2] Goto("SIP/3126255599-09d7e608", "ext-did|s|1") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Goto (ext-did,s,1)
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:1] Set("SIP/3126255599-09d7e608", "__FROM_DID=s") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:2] Gosub("SIP/3126255599-09d7e608", "app-blacklist-check|s|1") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@app-blacklist-check:1] LookupBlacklist("SIP/3126255599-09d7e608", "") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@app-blacklist-check:2] GotoIf("SIP/3126255599-09d7e608", "0?blacklisted") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@app-blacklist-check:3] Return("SIP/3126255599-09d7e608", "") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:3] GotoIf("SIP/3126255599-09d7e608", "1 ?cidok") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Goto (ext-did,s,5)
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:5] NoOp("SIP/3126255599-09d7e608", "CallerID is "***** " <312*******>") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:6] Set("SIP/3126255599-09d7e608", "__CALLINGPRES_SV=allowed_not_screened") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:7] SetCallerPres("SIP/3126255599-09d7e608", "allowed_not_screened") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ext-did:8] Goto("SIP/3126255599-09d7e608", "ivr-2|s|1") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Goto (ivr-2,s,1)
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:1] Set("SIP/3126255599-09d7e608", "LOOPCOUNT=0") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:2] Set("SIP/3126255599-09d7e608", "__DIR-CONTEXT=default") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:3] Set("SIP/3126255599-09d7e608", "_IVR_CONTEXT_ivr-2=") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:4] Set("SIP/3126255599-09d7e608", "_IVR_CONTEXT=ivr-2") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:5] GotoIf("SIP/3126255599-09d7e608", "0?begin") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:6] Answer("SIP/3126255599-09d7e608", "") in new stack
[May 15 09:43:00] VERBOSE[2743] logger.c: -- Executing [s@ivr-2:7] Wait("SIP/3126255599-09d7e608", "1") in new stack
[May 15 09:43:01] VERBOSE[2743] logger.c: == Spawn extension (ivr-2, s, 7) exited non-zero on 'SIP/3126255599-09d7e608'
[May 15 09:43:01] VERBOSE[2743] logger.c: -- Executing [h@ivr-2:1] Hangup("SIP/3126255599-09d7e608", "") in new stack
[May 15 09:43:01] VERBOSE[2743] logger.c: == Spawn extension (ivr-2, h, 1) exited non-zero on 'SIP/3126255599-09d7e608'

Any ideas anyone?



b14ck
Posts: 773
Member Since:
2009-03-03
I don't see anything

I don't see anything meaningful in those logs, but I bet I know what is causing the problems. Are you using analog lines? If so, talk to your provider and ask them about call hunting.

--

Randall Degges
Lead Developer, RCI Telecommunications
projectb14ck - http://projectb14ck.org/ - Weblog



indie
Posts: 3
Member Since:
2008-08-18
No, we're using BroadVoice

No, we're using BroadVoice on a standard DSL internet connection



witdirect
Posts: 35
Member Since:
2008-05-29
Anonymous call arebeing rejected

In your general settings change the anonymous call to yes and that should fix the problem. Some providers will act that way with accept anonymous call is set to no.



indie
Posts: 3
Member Since:
2008-08-18
Tried the switch to allow

Tried the switch to allow anonymous . . . no luck.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.