[Home]

Summary:ASTERISK-25799: can't place calls to throught sip trunk to cisco
Reporter:Rachid HIGUI (rhigui)Labels:
Date Opened:2016-02-17 10:40:20.000-0600Date Closed:2016-02-17 10:43:19.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Addons/General
Versions:1.8.25.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:I have set up a sip trunk between Asterisk (192.5.0.207) and Cisco Cucm 7.1 (192.5.0.201)
Extensions can call each other.
Cisco ip phones can call Asterisk softphones.

The problem is that Asterisk softphones can't call Cisco ip phones

Below is a sammury of the log:

[Feb 17 08:08:31] VERBOSE[22054] app_dial.c:     -- SIP/trunk_1-0000001d is circuit-busy
[Feb 17 08:08:31] VERBOSE[22054] app_dial.c:   == Everyone is busy/congested at this time (1:0/1/0)
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Executing [s@macro-trunkdial-failover:35] Set("SIP/800-0000001c", "num=4") in new stack
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Executing [s@macro-trunkdial-failover:36] GotoIf("SIP/800-0000001c", "0>0?s-CONGESTION,1:s-out,1") in new stack
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Goto (macro-trunkdial-failover,s-out,1)
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Executing [s-out@macro-trunkdial-failover:1] ExecIf("SIP/800-0000001c", "0?System(/etc/scripts/faxlog.sh    "FAILED" "CONGESTION")") in new stack
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Executing [s-out@macro-trunkdial-failover:2] StopMixMonitor("SIP/800-0000001c", "") in new stack
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:     -- Executing [s-out@macro-trunkdial-failover:3] Congestion("SIP/800-0000001c", "10") in new stack
[Feb 17 08:08:31] VERBOSE[22054] app_macro.c:   == Spawn extension (macro-trunkdial-failover, s-out, 3) exited non-zero on 'SIP/800-0000001c' in macro 'trunkdial-failover'
[Feb 17 08:08:31] VERBOSE[22054] pbx.c:   == Spawn extension (DLPN_DialPlan1, 486, 1) exited non-zero on 'SIP/800-0000001c'
Comments:By: Asterisk Team (asteriskteam) 2016-02-17 10:40:22.818-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Joshua C. Colp (jcolp) 2016-02-17 10:43:11.450-0600

It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists.

Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported.
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions