TCP trunk registration issue

[RichardDCG]

Within a tenant setup, setting trunks to use TCP for registration seems to use the wrong inbound trunk.  V68.0.20.  I can run a PCAP on the trunk that is used and it shows the correct invite, but the contact is the incorrect trunk.  Changing back to UDP then seems ok....

[RichardDCG]

is this just my PBX setup?  It is a pretty standard config ....

[Vodia PBX]

The PBX should tag the TCP connection with a trunk name, if there is one. I assume it is the same TCP connection like the registration? And the PBX is the TCP client? Then this should work like a charm without the need to guess what trunk this is. This is used for Teams where this seems to work fine. Are you using more than one SIP trunk for the same TCP address? Then it will indeed get tricky to figure out which trunk it is, though even that should be working if the trunk provider passed the line parameter along that was used for the registration.

[RichardDCG]

I have multiple trunks within a tenant.  If I use TCP for trunk registration then it seems to follow whichever is first in the list.  The inbound invite has the account and line details correct, but the call is routed inbound on the wrong trunk.  If I set back to UDP then all ok...

[Vodia PBX]

If there are multiple trunks, then the idea to use the TCP connection itself as trunk identifier does not work (that was expected). Also the identification by IP address does not work because they are all the same. The only way the trunk identification can work is by using the line parameter which is set to a random value during the registration. Can you see if this parameter is set when the trunk provider calls the PBX? Maybe just attach the INVITE here?

[RichardDCG]

SIP invite shows correct line .. but is received on a different trunk.

cant show a screen shot - not enough space.