The outbound calls do not use the user line identity for calls.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: [email protected]
<[email protected]>
To: [email protected] <[email protected]>
Sent: Fri Feb 19 16:03:58 2010
Subject: [sipx-users] outbound invite from conference system no called it
and internal never stops

Followed suggestion, created a user, put in a called it, assigned it to
a group that could make outbound calls, put the conference DID in as an
alias, forwarded the user to the internal conference extension, then
created the conference, gave it the extension.

dialing in works fine, either from the outside or inside.

the 'invite' has a couple of issues and I wanted to know where to start
tracking it down.
First, the outbound 'invite' cam from caller id 'unknown', even though
the user was assigned to a group that can make outbound calls and change
caller id.
Second, the internal invite (to another extension) rings forever.
(never goes to voicemail. I wonder what it would do with that),  no
status as to invites
(status should show in partitipents, I think), and no one can cancel
that invite.  The user finally answered it, but it just hung up.

Q: for conference bridges, what dial plan? what group do they try to
dial out of?
Q: if I used NAMES for user id's when creating this (as below) is that
why the caller id was unknown?
Q: if use digits for user name and conference name, what caller id would
show up?

I used the following guide when I created it.

   1.

      *Create a user*, {dept}_conf where dept is department, conf_sales
      for sales department (example, sales_conf).

   2.

      *Select a PIN code* (use alpha /numeric since we don't want
      external calls using this) this (user/pin code) will be used by
      sales manager(s) to log in and control conference.

   3.

      *Add to a group *(if you want it to be able to invite external users)

   4.

      *Put DID(s) in Aliases*, four ways: 1xxxxxxxxxx xxxxxxxxxx and
      xxxxxxx (1+10 digit, 10 digit and strip the area code off then 1+7
      digit.

   5.

      *Save*: Hit Apply

   6.

      *Set Call Forwarding* to internal extension (see dial plan), 'At
      the Same Time', Hit Apply

   7.

      *Select Caller ID* (outbound caller id, might use conference
      caller id, might default to). Hit Apply.

   8.

      *Create Conference,* conf_{dept}, internal extension as extension.
      In description, make sure you also use the 'DID (xxx) xxx-xxxx' in
      description. Example: Sales Conference line DID (xxx) xxx-xxxx.

   9.

      *Save*: You are done. Wait 30 seconds and try from inside and outside.


-- 
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 [email protected]
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