PRI congestion instead of busy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have two servers, each connected to the PTSN via PRI.  When I call from site A (951-999-9999) to site B (555-1212) and the phone at site B is on the phone, I hear the normal ring tone for about 20 seconds, then the message "all circuits are busy now.  please try your call again latter" followed by the congestion tone.  Instead, I want this to busy ring and then hang up without any message.

 

Here is a snippet from site A:

 

[2014-07-09 09:56:16] VERBOSE[21606][C-0000dab7] app_dial.c:     -- Called DAHDI/g5/5551212

[2014-07-09 09:56:17] VERBOSE[21606][C-0000dab7] app_dial.c:     -- DAHDI/i7/5551212-411b is proceeding passing it to SIP/260-0000a2f1

[2014-07-09 09:56:17] VERBOSE[21606][C-0000dab7] app_dial.c:     -- DAHDI/i7/5551212-411b is ringing

[2014-07-09 09:56:17] VERBOSE[21606][C-0000dab7] app_dial.c:     -- DAHDI/i7/5551212-411b is making progress passing it to SIP/260-0000a2f1

[2014-07-09 09:56:18] VERBOSE[21606][C-0000dab7] app_dial.c:     -- SIP/260-0000a2f1 requested media update control 26, passing it to DAHDI/i7/5551212-411b

[2014-07-09 09:56:37] VERBOSE[2286][C-0000dab7] sig_pri.c:     -- Span 7: Channel 0/3 got hangup request, cause 16

 

And from site B:

 

...

[2014-07-09 09:56:17] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s@macro-exten-vm:22] GotoIf("DAHDI/i8/9519999999-59f", "1?s-BUSY,1") in new stack

[2014-07-09 09:56:17] VERBOSE[3775][C-00000bb1] pbx.c:     -- Goto (macro-exten-vm,s-BUSY,1)

[2014-07-09 09:56:17] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s-BUSY@macro-exten-vm:1] GotoIf("DAHDI/i8/9519999999-59f", "0?exit,1") in new stack

[2014-07-09 09:56:17] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s-BUSY@macro-exten-vm:2] PlayTones("DAHDI/i8/9519999999-59f", "busy") in new stack

[2014-07-09 09:56:17] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s-BUSY@macro-exten-vm:3] Busy("DAHDI/i8/9519999999-59f", "20") in new stack

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] app_macro.c:   == Spawn extension (macro-exten-vm, s-BUSY, 3) exited non-zero on 'DAHDI/i8/9519999999-59f' in macro 'exten-vm'

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:   == Spawn extension (from-did-direct, 803, 2) exited non-zero on 'DAHDI/i8/9519999999-59f'

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [h@from-did-direct:1] Macro("DAHDI/i8/9519999999-59f", "hangupcall,") in new stack

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s@macro-hangupcall:1] GotoIf("DAHDI/i8/9519999999-59f", "1?theend") in new stack

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:     -- Goto (macro-hangupcall,s,3)

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s@macro-hangupcall:3] ExecIf("DAHDI/i8/9519999999-59f", "0?Set(CDR(recordingfile)=)") in new stack

[2014-07-09 09:56:37] VERBOSE[3775][C-00000bb1] pbx.c:     -- Executing [s@macro-hangupcall:4] Hangup("DAHDI/i8/9519999999-59f", "") in new stack

...

 

 

My hunch is that the PRI cause is never set, so site A gets the generic cause 16 (normal call clearing) instead of 17 (user busy).  I suspect this is causing site A to get the "all circuits are busy now" message instead of a busy signal.  I thought calling Busy() would cause the PRI cause to get set when used on a channel that is PRI?  Should this be manually set instead?

 

 

Site B details:

Asterisk version 11.10.2

Libpri version: 1.4.12

DAHDI version: 2.9.0.1

Freepbx version: 2.11.0.37, distro version 5.211.65-14

 

-Justin

 

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[Index of Archives]     [Asterisk Announcements]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite News]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]