How can a call drop with reason UNALLOCATED_NUMBER

Status
Not open for further replies.

finebytes

New Member
Sep 12, 2019
6
0
1
40
Inbound calls drop after exactly 1 minute. The call status UNALLOCATED_NUMBER.

1674319837215.png
How is that possible?
Since the call is made, and connection established, the "Unallocated number" status, doesn't really make sense
 
Last edited:

finebytes

New Member
Sep 12, 2019
6
0
1
40
Apparently it was a problem with the VoIP client I was using.
SIPSorcery, has a setting we didn't understand at first, that makes the underlying transport exclusive to the current UserAgent. For some memory/threading optimizations.
And since our application was using multiple UserAgents, simultaneously, we would get in a weird state, that would culminate in the result posted above.

Putting in place the correct configuration for our use-case fixed that problem for good!
 
Status
Not open for further replies.