Agreed.

 

The advice I got was to create a user for each DID (I named mine DID001,
DID002, etc.)

 

For each user that represents a DID number, add the number to the
"Aliases".   I added the number three times in the alias field, once
with 7 digits (no area code), once as 10 digits (area code + number) and
once as 11 digits (1 + area code + number) to cover the bases.

 

Then use the forwarding rules to forward calls to the conference bridge.

 

 

 Mike Burden

 
Lynk Systems, Inc

 e-mail: m...@lynk.com <mailto:m...@lynk.com> 

 Phone: 616-532-4985








 

From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony
Graziano
Sent: Thursday, February 18, 2010 2:49 PM
To: Michael Scheidell
Cc: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] did inbound to conference

 

 

On Thu, Feb 18, 2010 at 2:41 PM, Michael Scheidell <
scheid...@secnap.net> wrote:



On 2/18/10 2:36 PM, Scott Lawrence wrote: 

 

See 
 
http://wiki.sipfoundry.org/display/xecsuserV4r0/How+to+configure+Direct+
Inbound+Dialing+(DID)#HowtoconfigureDirectInboundDialing(DID)-DefiningaD
IDprefixDialingRule
 
for how to strip numbers from an inbound DID.
 
  

yuck, dial plan rules.  I did all this without dial plan rules.
I don't have ANY inbound dial plan rules (yet)





-- 
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> | SECNAP Network Security Corporation 

*       Certified SNORT Integrator
*       2008-9 Hot Company Award Winner, World Executive Alliance
*       Five-Star Partner Program 2009, VARBusiness
*       Best Anti-Spam Product 2008, Network Products Guide
*       King of Spam Filters, SC Magazine 2008

 

________________________________

This email has been scanned and certified safe by SpammerTrap(r). 
For Information please see http://www.secnap.com/products/spammertrap/

________________________________

 


_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/



You start necessitating this yourself by creating the line number as the
DID number. If your account extensions were normal (3 or 4 digit) none
of this would be necessary. 

 

DELETE the phantom user and conference. CREATE both as 3 or 4 digits as
per your internal dial plan. ADD the alias for the DID to the phantom
user, forward the phantom user to the 3 or 4 digit conference.

 

This IS_THE_WAY to achieve no necessitating an internal dial plan. Once
you start to create chaos, you will be forced to deal with it every day.


<<image001.jpg>>

<<image002.gif>>

_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to