Siddardha, One more major issue I see with the approach of Local Routing is "Features (Custom Ring-back Tone, Privacy Screening, forwarding etc) provided by the Service Provided are not considered while delivering the call"
So as suggested path-header is the approach. But if the intention is to avoid billing by making the local calls not visible to Service Provider then Path-header also will not help. Also depends on the support for the Path-header in the Service-Provider's Network. Kasturi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Siddhardha Garige Sent: Tuesday, April 10, 2007 8:37 AM To: Gaurav Kheterpal; [email protected]; [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Outbound proxy with local routing Gaurav, thanks for you time and reply. I went through rfc 3327 and I did not quite understand how I can use path header to eliminate local registration. Do you mind explaining me little more on this pls? -Siddhardha Gaurav Kheterpal <[EMAIL PROTECTED]> wrote: Inline. Regards, Gaurav -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Siddhardha Garige Sent: Thursday, April 05, 2007 6:31 PM To: [email protected] Subject: [Sip-implementors] Outbound proxy with local routing Hello all, I have a special requirement and just wondering if anyone has any Idea about this. Currently UACs are registering to a VoIP terminator. Account provisioning is done at terminators network. Client is getting billed for local calls too. Solution I am thinking of is to build a outbound proxy with local routing capabilities. UACs send registrations to outbound proxy and outbound proxy forwards them to VoIP service provider proxy. When 200OK for registration arrives, outbound proxy make an entry in local registration table. It maintains a copy of registrations on sip proxy. >> In essence, you are maintaining a cache of the service provider's registrar. There's nothing wrong/ violating any RFC as long as the entries in the local (or outbound) proxy's registration table are coherent with the actual registrar. To avoid this overhead, I think you are better off using the PATH header (RFC 3327) When a INVITE is received from UAC outbound proxy looks for callee in registration table. If callee is present in registration table, invite will be routed locally and if callee is not present then INVITE will be forwarded to proxy. >> The term outbound proxy is misleading as the registration table is >> used to determine where to forward INCOMING INVITES. It is inbound proxy functionality. Is it a good solution? >> Try using PATH header if it fits your requirements. Duplicating the REGISTRAR functionality does not sound like a efficient solution. am i violating any RFC rules? >> Probably not. BTW. we are thinking of using OpenSER and modify it according to our requirements. >> Good Luck !! Thanks in advance, -Sid "May the light be with you." ______________________________________________ Siddhardha Garige www.luminepixels.com --------------------------------- 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors "May the light be with you." ______________________________________________ Siddhardha Garige www.luminepixels.com --------------------------------- Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
