[Serusers] more about record route

[Greg Fausak]

I have a hard time articulating my real question :-)

What I was asking was :

As long as I record route an INVITE, does that make
everything else record-routed (meaning that I pick it up with
the loose_route())?

The answer is no, you still have to route calls...loose_route()
doesn't pick up everything.

Anyway, here is a packet trace from a call.

1) Inbound, through a PSTN.
2) Routed to the UA.
3) The caller hangs up, causing a cancel.

Does the trace look right?  In particular, the CANCELing 200
message and the cancelled 487...is that the way it is supposed
to look?

---greg


Jan Janak wrote:

> On 03-01 11:58, Greg Fausak wrote:
> 
>>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.
> 
> 
>   Only BYE/ACK. CANCELs are not record routed (since no 200 OK was
>   received by the sender). But because CANCEL contains the same
>   Request-URI as the associated INVITE, it is OK.
> 
>   But yes, you can record-route INVITEs only, that's probably what you
>   are interested in.
>  
>     Jan.
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
> 

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: eth1.txt
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040111/35caaf31/attachment.txt>