[OpenSIPS-Users] Identify an in progress call

[Muhammad Shahzad]

I had a similar problem a while ago and i deal with it in my own way, which
was quite simple actually.

1. First INVITE comes in, i check it does not has to_tag, i put its call-id
in memcache and do normal processing.
2. For subsequent INVITE without to_tag, i check in memcache if call-id
already exists, if yes then send stateless reply 100-Trying and exit.
Otherwise treat it as first INVITE.
3. Memcache auto expires each record after 60 seconds, so we have auto
clean up regardless if call was successful or failed.

If there is any better way, i would be happy to learn it.

Thank you.


On Thu, Aug 16, 2012 at 7:25 AM, Andrew Mason <andrew.mason at voice.net.au>wrote:

> Hi All,
> We recently encountered an issue in our datacenter where an upstream switch
> between the CPE and the OpenSIPS server was dropping packets. Obviously for
> VoIP this is not ideal but it did expose an issue in our configuration.
>
> If the packet dropped was a '183 Session Progress' or a 'Ringing' then the
> CPE
> would send the same Invite (exact same packet) to which our server issues a
> 407 Proxy Auth Required. At which stage the CPE seems to hang up.
>
> My question: How can I determine if a call is already in progress for a
> particular Invite ?
>
> Apologies if my terminology is not correct, please let me know if anything
> does not make sense. I have inherited this system and am still very much
> learning about SIP and OpenSIPS.
>
> Thanks in advance
> Andrew
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +92 334 422 40 88
MSN: shari_786pk at hotmail.com
Email: shaheryarkh at googlemail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120816/72c27e70/attachment.htm>