Bogdan-Andrei Iancu wrote:
was referring to a forking scenario:
UAC P UAS
<----------------- 180 from UAS1
<-------------- <----------------- 183 from
UAS1
<--------------
<----------------- 180 from UAS2
<---x---x---x-- this will not be relayed to UAC since a
higher reply code was already sent,
so the UAS2 will not be visible
regards,
bogdan
Klaus Darilion wrote:
First of all the UAC may not discover all the branches based on
To-tag - there might be branches that haven't sent any reply, or
replies were absorbed by the forking server (ex: 180 after 183 will
not be relayed).
Is this standard conform? What about
UAC P UAS
<----------------- 183 from UAS1 <--------------
???? 180 from UAS1 <--------------
Will this be forwarded?
klaus
Really? Why not? This is strictly valid and make sense. All gateways
does this:
INVITE --> SETUP
...
183 <-- PROGRESS w/ inband audio
180 <-- ALERTING
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
