When I only put one URI in the array, it worked fine.
I'd like to put a couple routes for SIP trunking failover. But it always did parallel forking.
My UriSet is a simple Erlang array of binaries representing uris. According to the doc, serial forking is expected. Not sure what's missing.
02:15:17.996 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) UAS 5335593001 'INVITE' route reply: {proxy,[<"sip:+1647xxxxxxx@toronto4.voip.ms">,<<"sip:+1647xxxxxxx@toronto5
.voip.ms">>],[record_route,follow_redirects]}
02:15:18.005 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) Fork 5335593001 'INVITE' started from UAS ([record_route,follow_redirects])
02:15:18.005 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) Fork 5335593001 'INVITE' launching next group
I'm using v0.5.0.
When I only put one URI in the array, it worked fine. I'd like to put a couple routes for SIP trunking failover. But it always did parallel forking.
My UriSet is a simple Erlang array of binaries representing uris. According to the doc, serial forking is expected. Not sure what's missing.
02:15:17.996 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) UAS 5335593001 'INVITE' route reply: {proxy,[<"sip:+1647xxxxxxx@toronto4.voip.ms">,<<"sip:+1647xxxxxxx@toronto5 .voip.ms">>],[record_route,follow_redirects]} 02:15:18.005 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) Fork 5335593001 'INVITE' started from UAS ([record_route,follow_redirects]) 02:15:18.005 [debug] server (de43d655-1f32-1235-fa83-0401c20ee801) Fork 5335593001 'INVITE' launching next group
Great project! I really like the concept.