NethVoice Proxy: Incoming SIP Call Termination Fails Due to Inconsistent BYE Request-URI with Voipvoice Provider

[Amygos]

When handling incoming calls on NethVoice via Voipvoice’s Voipvoicetel
service, call termination attempts result in a rejected BYE request. According
to the provider, the BYE issued by NethVoice uses an inconsistent Request-URI,
causing their server to refuse it. This prevents the external caller’s call
from ending properly and results in a hung line.

Steps to reproduce

1. Configure a NethVoice with a Voipvoice Voipvoicetel line.
2. Receive an incoming call on the Voipvoicetel line.
3. Attempt to hang up/end the inbound call from the NethVoice.

Expected behavior

The NethVoice system should terminate the call by sending a SIP BYE request
with a Request-URI that matches the Contact header from the original INVITE,
ensuring correct call closure with the provider, even when multiple
Record-Route headers are present.

Actual behavior:

The BYE request generated by NethVoice uses the original signaling source IP as
the Request-URI, ignoring the Contact from the INVITE. With multiple
Record-Route headers (as in this provider’s scenario, four are present),
Voipvoice rejects the BYE as incoherent, causing the call to remain open on the
caller’s side.

See also:

• Evoseed ticket: https://evoseed.atlassian.net/servicedesk/customer/portal/5/EA-61
• Private Mattermost discussion: https://mattermost.nethesis.it/nethesis/pl/kfkuckiugig63dpse9gzum9ruw

[margit86]

All the cases shown in the table have been verified.

Call Type	Closes	Status
Outgoing call	A	OK
Outgoing call	B	OK
Incoming call	A	OK
Incoming call	B	OK