Jump to content

TCP trunk registration issue


Recommended Posts

  • 2 weeks later...

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...