[Asterisk-Users] New Asterisk bounty: SIP simultaneous

[Jason Penton]

Well Andres is right but there are numerous problems with quite a few SIP
clients that do NOT follow the the SIP RFC correctly. There is a problem
with dialog creation in a number of SIP products out there. SIP dialog
creation is the critical part of the spec that supports parallel forking -
so be careful.

Jason 

> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com 
> [mailto:asterisk-users-admin at lists.digium.com] On Behalf Of Andres
> Sent: 12 July 2004 08:54 AM
> To: asterisk-users at lists.digium.com
> Subject: Re: [Asterisk-Users] New Asterisk bounty: SIP simultaneous
> 
> 
> >So isn't this the problem * has? The first client registers 
> as the address
> >of record, then the second client comes in with the same 
> registration and
> >becomes the address of record? 
> >
> >  
> >
> I think you are making this look more complicated than it 
> actually is.  
> We do this with our SER Network all the time.  Its called "parallel 
> forking".   For example, our subscribers can have 2 or more 
> Sipuras with 
> the same number and registration info.  They have one Sipura at the 
> office and another at home.  When a call is destined for that 
> sub, SER 
> will lookup the location database to see where it should send the 
> INVITE.  If it sees 2 or more locations then it sends 
> multiple INVITES, 
> ie.. "Parallel Fork".  The first INVITE to answer will be the 
> one that 
> establishes the RTP Session and all the others will receive a CANCEL. 
> 
> Its quite simple and works perfectly. 
> 
> -- 
> Andres
> Network Admin
> http://www.telesip.net
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
>