He's in that there nightmare place. I think that's an idea for an improvement request. Show the user caller id or branch when dialing 911 for this group, and disable callerid blocking when that kind of call is made... One group and tell it to use user callerid in the account, assign everyone to the group...
On Tue, May 11, 2010 at 11:50 AM, Paul Herron <[email protected]>wrote: > Tony’s earlier points notwithstanding, perhaps you could address your > problem by establishing separate “branches/gateways” pointing to unique > subaccounts with your ITSP for each user requesting anonymous caller ID. Of > course, if you have a very large user base, this quickly becomes an > administrative nightmare. > > From: Jeff Gilmore [mailto:[email protected]] > Sent: Sunday, May 09, 2010 5:10 PM > To: Sipx-users list > Subject: [sipx-users] Challenges with caller-ID blocking > > I am resending this to the list, as I did not see it come back and have > been having some email problems. Forgive me if you have read it already (but > feel free to chime in if you have any insights)! > > ============ > > I have been working with my ITSP to resolve problems for my users that > choose to have outbound caller ID (CLID) blocked. We are finding that the > way sipx (4.0.4) handles blocking CLID also interferes with 911 service. > > My ITSP explains it as such: > > According to RFC3325, when sending an invite to a "trusted gateway", the > header field P-asserted-identity should be included and should contain the > actual identity information (in my case, I need it to send the DID) and the > "Privacy" field set to "ID", indicating that the receiving gateway should > not share the identity with any non-trusted gateways. Here is an example > from the RFC: > > From: "Anonymous" <sip:[email protected]>;tag=9802748 > > Call-ID: 245780247857024504 > CSeq: 2 INVITE > Max-Forwards: 69 > P-Asserted-Identity: "Cullen Jennings" > <sip:[email protected]<sip%[email protected]> > > > P-Asserted-Identity: tel:+14085264000 > Privacy: id > > In my case, it appears that I am sending the username with which I > authenticate with the ITSP (this single username is used for all outbound > calls from any of my users, and there is no pre-registration) in the > P-asserted-identity field, no "Privacy" header, and > "sip:[email protected]" in the from field. > > Since we do not send the real DID anywhere in the header, this means that > the DID is unavailable for 911 service lookup if CLID is disabled. > > Can anyone help me figure out how to get sipx to include the DID (which I > set manually for each user as their Caller-ID string) in the > P-asserted-identity header? > > I also am wondering about trust domains. I don't see any configuration > fields in the SBC or gateway that allows me to indicate whether or not I > consider the gateway part of my trust domain. Is sipx behaving this way > because it considers my ITSP untrusted? If so, how can I indicate trust > status? > > Any insights would be helpful. I can send more config and trace details > privately, if needed. > > Thanks, > > Jeff > > > _______________________________________________ > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
