Kamailio SIP Proxy Anti-Buzón para canales ilimitados

@ivicab6

As an experienced full-stack engineer, I may not have specific experience in Kamailio and SIP routing like some other profiles, but I strongly believe my skill set can be quite beneficial for this project. Throughout my 6+ years of experience, I have become adept at quickly learning and adapting to new technologies and systems, which will be invaluable as we tackle the task at hand. Moreover, my proficiency in troubleshooting, SQL, and data handling will be instrumental in not only implementing Kamailio as desired but also providing additional features that may enhance its functionality. For instance, if you require statistics beyond what is laid out in the project's scope, I can create reports or dashboards that offer more detailed insights into the call blocking process. This could help identify trends or patterns in blocked calls that may not be immediately apparent. Lastly, I'm passionate about automating processes to improve efficiency and effectiveness. This resonates with your objective to reduce manual work and eliminate calling costs prior to charging by solely employing SIP signaling. Let's work together and solve this challenge. In the end, my goal is to deliver a solution that not only meets but exceeds your expectations by ensuring optimized performance whilst reducing operational errors. Let's leverage my diversified expertise for your project's success!

@amadorjay

Hello, The primary engineering challenge involves accurately detecting call diversion to voicemail before the 200 OK response. This requires precise filtering based on various SIP headers and patterns, which can introduce complexities in SIP routing and state management. Additionally, ensuring the system can handle potentially unlimited concurrent channels while maintaining performance and reliability will be critical. The architecture must effectively support these requirements without compromising security or stability. Could you clarify how the filtering rules should be prioritized? Are there existing SIP trunks we need to integrate with, or will new ones be set up? What specific logging requirements do you have for blocked calls? Looking forward to discussing the architecture further.

@CorranForce

Hello! Allen from Fort Worth here. I understand that the goal is to implement a high-performance Kamailio SIP proxy to prevent toll charges by intercepting and dropping calls redirected to voicemail before a 200 OK is received. The primary emphasis should be on meticulous SIP header inspection and prompt response handling to ensure zero-latency routing for authorized traffic. The project will be developed by configuring a specialized Kamailio script that uses the textops and pv modules to parse Diversion, History-Info, and carrier-specific headers. Q1. Since different carriers use non-standard headers or proprietary values to signal voicemail, do you have a collection of PCAP files or sngrep logs from your current providers to ensure we capture every possible redirection pattern? Q2. For the 1,000+ concurrent channel requirement, are you planning to deploy this on a bare-metal server or in a virtualized environment? This affects how we tune the Kamailio shared memory and child processes for peak stability. Q3. Regarding the whitelist/blacklist, would you prefer a dynamic reload capability via RPC so you can update carrier rules in real time without restarting the Kamailio service or dropping active calls? I'm excited to hear from you soon! Best wishes.

@johibkhan

Hi, With over a decade and a half’s experience as a VoIP/SIP engineer and proven expertise in Kamailio, SIP routing, and managing carrier SIP trunks, I believe my skills are perfectly aligned to your project requirements. Throughout my career, I have excelled at working with high concurrency and troubleshooting complex VoIP scenarios using tools like sngrep, tcpdump, and SIPp – tools that will undoubtedly prove crucial for effectively implementing your Kamailio anti-voicemail proxy. My track record at illustrious names such as Avaya, Pramati, and CGI reflect my competence in building scalable architectures and high-performance systems that can handle extensive data volumes in real-time. For your project's needs for logging, blocking rules based on Diversion, History-Info, 181 Call Is Being Forwarded signals, and more I have the necessary practical exposure to design robust strategies. Advanced troubleshooting to ensure unobstructed service through correct configuration of headers real-time monitoring is 유전자