Verdict

“The PBX configuration and potential SIP trunking offer a viable path to preserve caller ID, creating a monetizable service for the hotel.”

The core issue revolves around the NEC UNIVERGE SV9300 PBX and its interaction with the carrier's ISDN PRI line. The PBX is likely stripping or not forwarding the original caller ID due to configuration settings or limitations. While the carrier claims they cannot pass the original caller ID, the PBX might have settings to preserve this information. Exploring SIP trunking directly from the PBX to the destination could bypass the carrier's limitations, but this requires the PBX to support SIP and proper configuration to maintain caller ID. The potential revenue model here involves offering a solution to the hotel for a fee, such as configuring the PBX to forward calls via SIP or negotiating with the carrier for a premium service that preserves caller ID. The unit economics would involve a one-time setup fee and possibly a monthly service charge for maintaining the solution.

“Carrier limitations and outdated PBX hardware make this problem unsolvable without Ooredoo Qatar's direct intervention.”

The core issue is that the hotel's carrier (Ooredoo Qatar) is stripping or failing to pass the original caller ID during forwarding, and the NEC UNIVERGE SV9300 PBX lacks the capability to preserve it independently. The carrier's refusal to enable caller ID on forwarding is a hard technical limitation, not a configuration issue. Even if the PBX were upgraded or reconfigured to use SIP trunking directly, the older hardware may lack the necessary SIP headers (Diversion, History-Info) to propagate the original caller ID reliably. Additionally, the hotel's contract with Ooredoo likely restricts network-level forwarding, forcing reliance on the carrier's cooperation. Without carrier-side changes, no PBX tweaks or workarounds (like SIP trunking) will fully resolve this, as the original caller ID is lost before it reaches the destination. The risk of churn is high if the hotel or its guests rely on caller ID for operations or security.

“A dedicated ISDN - PRI to SIP caller - ID preservation gateway is the only realistic way to keep the original number alive, and it offers a narrow but defensible niche if positioned as a turnkey solution for legacy hotel PBXs.”

The core issue - lost caller ID on PBX - to - PSTN forwarding - is a known pain point for hotels using legacy NEC UNIVERGE systems with ISDN PRI. Several existing approaches can address it: (1) virtual PBX or cloud - telephony providers (RingCentral, Grasshopper, CallRail) that terminate the call on their own platform and forward to the hotel, preserving the original number via their own outbound trunk; (2) SIP - SBC solutions (Cisco, Audiocodes, Sonus) that can rewrite the From/P - Asserted - Identity headers using the ISDN calling - party number if the PRI is tapped; (3) outright replacement of the ISDN PRI with a SIP trunk, which eliminates the forwarding step entirely but requires PBX or carrier changes. Because the hotel's PBX and carrier contract are out of the entrant's control, any durable differentiation must sit outside those constraints. A niche gateway that sits between the hotel's PRI line and the cloud voice platform, extracts the ISDN Calling - Party Number (CIP) from the Q.931 SETUP message, and injects it into the SIP INVITE before the call reaches the UCM6302 would be a concrete, technically feasible solution that few current services offer specifically for this legacy stack. However, the market for such a dedicated gateway is small, and larger SBC vendors can quickly add similar functionality, meaning the advantage is not strongly proprietary. Consequently, while the idea solves a real problem, the differentiation is modest and vulnerable to competition from existing SBC or cloud - PBX solutions.

“Without the hotel's PBX or its carrier preserving the original caller ID on ISDN PRI forwarded calls, the caller ID is irreversibly lost and cannot be reconstructed downstream.”

The core issue is that the hotel's NEC UNIVERGE SV9300 PBX forwards calls over an ISDN PRI line, and the carrier strips the original calling party number before the call reaches the forwarding destination. In ISDN PRI, caller ID preservation on forwarded calls depends on the PBX sending a proper CALLING PARTY NUMBER IE in the SETUP message and the carrier supporting CLIP (Calling Line Identification Presentation) on forwarded calls. The carrier explicitly states it cannot pass the original number on forwarded calls for this line type, and the PBX is not adding any diversion or history-info headers that could carry the number. To solve this, one would need either (a) PBX configuration to send the original number in the forwarding SETUP (often a feature like 'Call Forwarding with CLIP' or 'Transparent Forwarding'), which requires access to the PBX admin interface and possibly a firmware update, or (b) carrier - level network forwarding that preserves CLIP, which the carrier denies is possible on PRI. Alternatives involve bypassing the PRI entirely: installing a media gateway or SIP - to - PRI converter at the hotel to convert the PRI trunk to SIP, then forwarding the SIP call directly to the Vodafone trunk while preserving the From header. This approach needs physical access to the hotel's premises, power, and configuration of the gateway, as well as coordination with the hotel's IT staff. For a solo or two - person team, gaining that access, procuring and configuring a gateway, and testing within 4-12 weeks is challenging but not impossible if the hotel cooperates. However, without PBX or carrier cooperation, the software - only solution on the receiving side cannot recover the missing caller ID, making the problem fundamentally unsolvable from the cloud side alone. Overall feasibility is low.

“The core opportunity lies in helping hotels replace PRI forwarding with SIP - based call routing that preserves caller ID, but success hinges on gaining PBX access or carrier cooperation, which are significant barriers.”

The idea addresses a real technical pain point: loss of original caller ID when a legacy PBX forwards calls via ISDN PRI to an external SIP trunk. Hotels and other businesses that rely on call routing for reservations, guest services, or support need accurate caller identification for CRM integration, call analytics, and personalized service. However, the market is constrained to organizations still using TDM - based PBXs with PRI lines that do not support network - level forwarding and whose carriers refuse to pass the original number. In the GCC region, many larger hotels have migrated to VoIP or hybrid systems, reducing the addressable base. Solving the problem would require either PBX - side configuration (e.g., enabling SIP diversion headers, using SIP trunking instead of PRI, or deploying a media gateway that preserves the original number) or negotiating with the carrier for CLIP preservation - both of which are uncertain and may involve additional hardware or contract changes. Willingness to pay exists for a reliable, low - maintenance solution, but sales cycles are long due to dependence on third - party PBX access and carrier cooperation. Overall, the venture has a viable niche but limited scalability, warranting a moderate score.