Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it supposed to be serial? But it always did parallel forking. #70

Open
enst opened this issue Nov 7, 2016 · 1 comment
Open

Is it supposed to be serial? But it always did parallel forking. #70

enst opened this issue Nov 7, 2016 · 1 comment

Comments

@enst
Copy link

enst commented Nov 7, 2016

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:[email protected]">>,<<"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.

@enst enst changed the title Is it supposed to be serial? But it always do parallel forking. Is it supposed to be serial? But it always did parallel forking. Nov 7, 2016
@kalta
Copy link
Member

kalta commented Jan 14, 2019

Please check fork test on last version v0.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants