933 is usually just provided by the SIP carrier in my understanding. A lot of the circuits I've installed don't have 933 as an option.
On Tue, Jul 9, 2019 at 12:38 PM Jason Faraone <[email protected]> wrote: > We’re using the default address information – this TN is provided via > SIP.us, and so I manually entered in the E911 information when I > provisioned the line. I opened a ticket with them, and they verified that > the address they have on hand is the correct one, which I believe as 933 is > able to confirm this. > > > > My confusion comes in with 911 receiving different information – slightly > different, but enough to cause concern. I was always under the impression > that 933 and 911 pulled the same data when it comes to caller ID. > > > > > *Jason Faraone *Sr. Network Engineer Bear > > Build-A-Bear Workshop, Inc. > 1954 Innerbelt Business Center Drive > St. Louis, MO 63114 > US: 314.593.3244 > UK: 01753560740 > C: 314.308.9003 > > *[email protected] <[email protected]>* > www.buildabear.com > > *Follow us:* Facebook <https://www.facebook.com/Buildabear>, Twitter > <https://twitter.com/buildabear>, YouTube > <https://www.youtube.com/user/Buildabearworkshop1>, Pinterest > <https://pinterest.com/buildabear/> > > <http://www.buildabear.com/> <https://dashradio.com/buildabear> > > > > *From:* cisco-voip <[email protected]> *On Behalf Of *Lelio > Fulgenzi > *Sent:* Tuesday, July 9, 2019 11:31 AM > *To:* [email protected] > *Subject:* Re: [cisco-voip] E911 Address Incorrect > > > > Hey Jason, > > > > Do you subscribe to a PS-ALI type service? Or are you relying on default > address information? > > > > If you are relying on default address information – that will be difficult > to change since it’s likely going to be tied to the service address of the > PSTN connection. > > > > That being said, if it’s actually incorrect, you should be able to reach > out to your account team for starting point. First thing I’d do is check > with whomever is getting the bills for that PSTN number to see what the > billing information looks like. If they have equipment records, that might > help too. > > > > Lelio > > > > > > --- > > *Lelio Fulgenzi, B.A.* | Senior Analyst > > Computing and Communications Services | University of Guelph > > Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | > N1G 2W1 > > 519-824-4120 Ext. 56354 | [email protected] > > > > www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook > > > > [image: University of Guelph Cornerstone with Improve Life tagline] > > > > *From:* cisco-voip <[email protected]> *On Behalf Of *Jason > Faraone > *Sent:* Tuesday, July 9, 2019 12:09 PM > *To:* [email protected] > *Subject:* [cisco-voip] E911 Address Incorrect > > > > I have a location that shows the correct physical address when I dial 933, > but a slightly incorrect address when dialing 911. Has anyone encountered > this before? > > > > Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road. > Everything else is correct (State, CID, zip, street address). There is an > Oakbrook road in the area, so I need to get this resolved so that there is > no confusion in case of emergency. > > > > > *Jason Faraone *Sr. Network Engineer Bear > > Build-A-Bear Workshop, Inc. > 1954 Innerbelt Business Center Drive > St. Louis, MO 63114 > > > *[email protected] <[email protected]>* > www.buildabear.com > > *Follow us:* Facebook <https://www.facebook.com/Buildabear>, Twitter > <https://twitter.com/buildabear>, YouTube > <https://www.youtube.com/user/Buildabearworkshop1>, Pinterest > <https://pinterest.com/buildabear/> > > <http://www.buildabear.com/> <https://dashradio.com/buildabear> > > > > The information in this message may be privileged, "confidential" and > protected from disclosure and/or intended only for the addressee(s) named > above. If the reader of this message is not the intended recipient, or an > employee or agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of the communication is strictly prohibited. If you have received > this communication in error, please notify us immediately by replying to > the message and deleting it from your computer. Please consider the > environment before printing this email. > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
