Looks like the outbound caller id on the conference 'invite' is the
extension number of the conference, not the extention number and not the
caller id of the user who owns the conference.
since a conference does NOT need to be owned by any user, I suggest that
the conference needs a caller id, group membership and permissions.
I have sip traces for anyone who wants to see it or, try it.
easy to setup:
user sales_conf, aliases are the DID number of the inbound, call fwd to
the (soon to be assigned) conf_sales extension.
conference 'conf_sales', extension = 1673
dial into it, then from gui, invite someone.
CDR report from the itsp trunk provider confirms the caller id was the
conference extension number.
workaround was to move the conference extension as alias for user, call
fwd user to conference, and have conference extension be the DID number.
--
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/
