Provider certification record
Gaglers Inc dba CallHub
Listed- RMD number
- RMD0026043
- FRN
- 0036499440
- OCN
Identity
- Legal business name
- Gaglers Inc dba CallHub
- Doing-business-as
- CallHub
- Foreign Voice Service Provider
- No
- Business address
- 2093 Philadelphia Pike, #7468, Claymont DE 19703
- Filing contact
- Swaminathan B
CISO · Security & Compliance
compliance@callhub.io
(202) 318-7029
2093 Philadelphia Pike #7468 Claymont DE 19703
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Gaglers Software Pvt Ltd
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Summary For the reasons detailed below, we are classified under “No STIR/SHAKEN Implementation” (Option 3). However, we maintain a robust robocall mitigation program under 47 CFR § 64.6305(a) to ensure we monitor traffic for suspicious activity, respond promptly to traceback requests, and cooperate fully with law enforcement and industry traceback entities to combat illegal robocalling. Rule Citation / Exemption Basis The FCC’s rules (47 CFR § 64.6304) provide certain extensions and exemptions to the STIR/SHAKEN implementation requirement. Specifically, under § 64.6304(a) and (b), voice service providers that do not directly originate calls on an IP-based network and/or lack the technical capability to implement STIR/SHAKEN may qualify for an extension or exemption from STIR/SHAKEN requirements. Explanation No Direct IP Interconnection We do not operate an IP-based network that directly hands off calls to the PSTN. Instead, we hand off all calls to upstream telecommunications carriers, which hold numbering resources and maintain direct PSTN interconnections. Those carriers apply STIR/SHAKEN signing where applicable. No Facilities-Based Origination We do not originate calls under our own Operating Company Number (OCN) or numbering resources. We provide a software/aggregation platform that customers use to initiate calls, which are then handed to an underlying carrier for actual PSTN origination. Reliance on Upstream Compliance Because we do not control the final call-signaling path to the PSTN, we cannot technically implement STIR/SHAKEN on our own network. Instead, STIR/SHAKEN authentication is performed by the facilities-based carriers that actually originate the calls.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Swaminathan B
- Date
- 2025-01-09No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2025-01-09 | New | Initial certification filed and added to database. |