[Serusers] more about record route

[Greg Fausak]

I love this mailing list :-)

So, in my case where I am routing
phone calls and not doing any SUBSCRIBE/NOTIFY stuff,
my original assertion seems to be correct.

I need to handle 3 requests

1) a loose_route()
2) a REGISTER
3) an INVITE

The INVITE stamps all dialogs with a record route, all subsequent
BYE/ACK/CANCEL stuff rides on the loose_routing.  Anything
that doesn't match one of the 3 cases above is an error.

Right?

---greg


Juha Heinanen wrote:

> Maxim Sobolev writes:
>  > 
>  > Well, IMO absence or presence of tag in the To header field should be 
>  > the definite difference between the two. INVITE which creates a dialg 
>  > would be To-tag-less, while one that refreshes a dialog would usually 
>  > have one. And if my memory serves according to the RFC INVITE is the 
>  > only type of message which can create a dialog.
> 
> also subscribe and even notify can create a dialog.
> 
> -- juha
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
>