[asterisk-users] Issue dialing out

[Andre Goree]

>> They are either incompetant or lying to you. Call appears to succeed (it
>> is answered) and gets disconnected after 23s. You are not generating the
>> message, so the calls gets back to you telco.
>>
>> Most likely someone is filtering on callerID (which is a good thing IMHO).
>> Set the callerid to one of your numbers before sending it back to Zap
>> and try again.
>>
>
> You're right!  Forgot to update this thread, but a tech from their
> side performed a trap on the line and attempted to recreate the issue.
> From their switch, they're seeing the call go into our asterisk
> system, then leave the asterisk system (as it tries to dial the
> outside line when reaching the specific extensions 4832), then
> receiving a disconnect from our asterisk system almost immediately. So
> it would appear that asterisk attempts to forward the call as
> expected, then immediately disconnects for some unknown reason, which
> I guess is the specific issue I need to determine the cause of and
> resolve.
>
> I'm going to try what you've suggested and set the callerid to one of
> our numbers.  Will let you know of the result.
>
> Thanks!

Setting the CID did not work, unfortunately :(

Jun 15 14:50:31 VERBOSE[777]: -- Accepting call from 'XXXXXX6886' to
'XXXXXX3730' on channel 0/1, span 1
Jun 15 14:50:31 VERBOSE[31883]: -- Executing Answer("Zap/1-1", "") in new stack
Jun 15 14:50:31 VERBOSE[31883]: -- Executing Wait("Zap/1-1", "2") in new stack
Jun 15 14:50:33 VERBOSE[31883]: -- Executing Goto("Zap/1-1",
"pri-in-dids|XXXXXX3730|1") in new stack
Jun 15 14:50:33 VERBOSE[31883]: -- Goto (pri-in-dids,XXXXXX3730,1)
Jun 15 14:50:33 VERBOSE[31883]: -- Executing Goto("Zap/1-1",
"menu-v2|s|1") in new stack
Jun 15 14:50:33 VERBOSE[31883]: -- Goto (menu-v2,s,1)
Jun 15 14:50:33 VERBOSE[31883]: -- Executing BackGround("Zap/1-1",
"firstintro") in new stack
Jun 15 14:50:33 VERBOSE[31883]: -- Playing 'firstintro' (language 'en')
Jun 15 14:50:39 VERBOSE[31883]: == CDR updated on Zap/1-1
Jun 15 14:50:39 VERBOSE[31883]: -- Executing SetCIDNum("Zap/1-1",
"XXXXXX3730") in new stack
Jun 15 14:50:39 VERBOSE[31883]: -- Executing Dial("Zap/1-1",
"zap/g1/1XXXXXX2222|20|tT") in new stack
Jun 15 14:50:39 VERBOSE[31883]: -- Called g1/1XXXXXX2222
Jun 15 14:50:42 VERBOSE[31883]: -- Zap/2-1 answered Zap/1-1
Jun 15 14:50:42 VERBOSE[31883]: -- Attempting native bridge of Zap/1-1
and Zap/2-1
Jun 15 14:50:58 VERBOSE[777]: -- Channel 0/1, span 1 got hangup
Jun 15 14:50:58 VERBOSE[31883]: -- Hungup 'Zap/2-1'
Jun 15 14:50:58 VERBOSE[31883]: == Spawn extension (menu-v2, 4832, 2)
exited non-zero on 'Zap/1-1'
Jun 15 14:50:58 VERBOSE[31883]: -- Hungup 'Zap/1-1'

I'm going to try another number that we have through them in hopes
that it'll complete and I'll let you know if that works.  Do you have
any other suggestions on what you think they might be filtering by?

In the trap given to me by the company, they show our system issuing a
"disconnect" from our end, rather than their end dropping the call.

Thanks for the assistance.