Untitled Note

PBX: another SIP endpoint. Non-descript phone type, just as the existing phones on AP. Not API based, only SIP. wikis: Microsoft Teams 411 | RC cloud PBX admin URL ---- T2 case > ERL/911 | Unable to add emergency address Example: case# 18520625 1) verify the address on USPS | Smartstreet https://tools.usps.com/zip-code-lookup.htm?byaddress https://smartystreets.com/products/single-address 2) try to add the address again, check for typos 3) get HAR files (If the address was not updated even after creating the bandwidth ticket so that the development team can check it) 4) attach them to the Bandwidth case for ERL update. -------- Duplicate email 1) destroy the account 2) enable the account temporarily to remove the contact email ---------------- case# 18448317 UID: 63038785028 1) Telco Ops was asked to rebroadcast the #, but they were not able to do so because: "We can only re-provision/rebroadcast RCLEC numbers for Voice. Upon checking, Number 12029210225 is correctly provisioned on our end." Also, they advised to "Please escalate to tech support tier 2 to troubleshoot with our carrier (Lumen). Thanks." 2) Carrier Escalation Template Subject: Number 12029210225 is correctly provisioned on our end but it is unexpectedly forwarding calls to a trucking company– RC case # 18448317. Background: Checked call forwarding under ext 104, made sure there are no custom rules that can affect it, check the schedule, work hours, and after hours, double check the voicemail is the one for ext 104 and the recorded message is correctly set up. Problem Reported: Unexpectly forwarded to a trucking company when we call the ext 104 number (202) 921-0225, if we call the main company number and went through the IVR, when selecting key press 1 to get connected to ext 104 the call was successfully connected, the behavior is only when the number is directly dialed. Internal TT: RC case # 18448317. Call Examples: [at least 2] 1) Calling #:8888984591 Called #:2029210225 Date/Time: 5/18/2023 10:10 > CST | 16:10 Kibana Time Actual Behavior: Unexpectly forwarded to a trucking company when we call the ext 104 number (202) 921-0225, if we call the main company number and went through the IVR, when selecting key press 1 to get connected to ext 104 the call was successfully connected, the behavior is only when the number is directly dialed. Expected Behavior: Sent to the voicemail of extension 104 after hours and connect to the extension during work hours (Ingress Invites containing carrier IP Address): 18888984591@216.20.237.33:5060 (Egress Invites containing carrier IP Address): 18888984591@192.209.25.230:5060 Attachments: [Screenshots, SIP Ladder, PCAPs] 2) Calling #: 8888984591 Called #: 202 921 0225 Date/Time:5/18/2023 10:18 > CST | 16:18 Kibana Time Actual Behavior: Unexpectly forwarded to a trucking company when we call the ext 104 number (202) 921-0225, if we call the main company number and went through the IVR, when selecting key press 1 to get connected to ext 104 the call was successfully connected, the behavior is only when the number is directly dialed. Expected Behavior: Sent to the voicemail of extension 104 after hours and connect to the extension during work hours (Ingress Invites containing carrier IP Address): 18888984591@216.20.235.33:5060 (Egress Invites containing carrier IP Address): 18888984591@192.209.25.134:5060 Attachments: [Screenshots, SIP Ladder, PCAPs] **** After checking with NTD, the # is not active within RC anymore, it was ported over 10 days ago. That's why they have misrouting issues. We should be deleting the # on our end and referring the cx to the new carrier ONVOY, LLC - DC (not Lumen as stated on the previous case notes) > ITQN. Advised the cx to send an email to ntd.helpdesk@ringcentral.com to ask the agents from NTD to delete the # from the RingCentral account, they can also dispute the port out if they need to. After calling the cx to share my findings, he wants to dispute the port out because he's not aware when or how the port out request was submitted so I send him the information stated above to his contact email: lars@jdhowlettelaw.com Hello, Lars. The number in question (202 921 0225) was ported out of RingCentral on May 8th, 2023. Since you stated on our call that you are not aware of how the port-out request was submitted or who submitted it, please send an email to ntd.helpdesk@ringcentral.com to ask for the unauthorized port-out dispute. Best regards, Francisco. RingCentral TechSupport. CB #1: 464439537951