| Summary: | ASTERISK-00487: [patch] for extension selection based on distinctive ring for inbound calls via FXO | ||
| Reporter: | ww (ww) | Labels: | |
| Date Opened: | 2003-11-05 18:40:30.000-0600 | Date Closed: | 2011-06-07 14:05:27 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) chan_zap.c.dringpatch | |
| Description: | Two configuration parameters are introduced in zaptel.conf, dnid1 and dnid2. They are configured as follows: dnid1 => 15145551212 dnid2 => 15145551313 when a "normal" call comes in, the call is mapped to extension 15145551212. when a call on the second number comes in, with the distinctive ring, the call is mapped to 15145551313. these extensions must exist in the channel's context. the default value for dnid1 and dnid2 is 's' to preserve compatibility with old configs. ****** ADDITIONAL INFORMATION ****** requires callerid code, but shouldn't | ||
| Comments: | By: John Todd (jtodd) 2004-01-20 12:14:01.000-0600 Err... should this be closed? This is now in zapata.conf: ; ; Used for distintive ring support for x100p. ; You can see the dringX patterns is to set any one of the dringXcontext fields ; and they will be printed on the console when an inbound call comes in. ; ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel => 1 | ||