Best practices for parallel fork with redirect on one branch
Hey Guys, Have met a situation where I need to do parallel call forking with bridge application and on one of the legs will receive a 302 which could mean another parallel fork there. Have tested the following scenarios: 1. Sip profile with manual-redirect=true. Here I fork the call using bridge with "," as separator and parallel fork works. The issue is that as soon as one of my forked legs receives 302, the other will be cancelled also and 302 will be handled further in it's context. Is this the expected behaviour from bridge? Question here: should it drop one branch of the parallel fork if other is receiving redirect? 2. Sip profile with manual-redirect=false, leaving mod_sofia doing the handling of the redirect. After I fork the call here with bridge, only the leg which receives 302 will be redirected which is the expected behaviour by me. The issue I have here is that I do not know how to influence mod_sofia to handle parallel forking out of 302 and not very obvious out of the documentation I have digged so far (I receive 2 contacts in redirect btw which I would like to fork also here). Question here: may I specify the type of fork mod_sofia should do in some way? Thanks in advance for any tip! DanB PS: Logs available at request if needed.
participants (1)
-
DanB