mskenderian Posted August 19, 2022 Report Share Posted August 19, 2022 How can we change the Call ID in the sip messages, INVITE sip: Via: SIP/2.0/TCP From: To: Call-ID: d0b3386a@pbx I would want to send either {unique_call_id}@{pbx_name} OR {unique_call_id}@{pbx_ip_address} Quote Link to comment Share on other sites More sharing options...
koolandrew Posted August 20, 2022 Report Share Posted August 20, 2022 I would suggest reading the docs, as i am not even sure how to answer that question. Everything depends on your extension/trunk and if appropriate inbound trunk settings. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted August 21, 2022 Author Report Share Posted August 21, 2022 20 hours ago, koolandrew said: I would suggest reading the docs, as i am not even sure how to answer that question. Everything depends on your extension/trunk and if appropriate inbound trunk settings. yes I did that, I found settings to control from, to and other items, but Call-ID is a unique string that represents that particular call. it ends in "@pbx" which make it difficult to figure out which PBX it came from. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 24, 2022 Report Share Posted August 24, 2022 The SIP Call-ID that the PBX is generating pretty much hard coded. So are the ones that come e.g. from VoIP phones or SIP trunk providers. Apart from looking better is there any rationale behind changing SIP callerID? Quote Link to comment Share on other sites More sharing options...
mskenderian Posted August 24, 2022 Author Report Share Posted August 24, 2022 the logs i get from from the carrier, just saw that, hard to run distinguish which is which. ending in "@pbx" isnt good, why not hostname or IP? but i think i can also use x-tag for better mapping of which pbx. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 24, 2022 Report Share Posted August 24, 2022 There is no such thing as the IP address on a modern server. There are many! Private, loopback, IPv4, IPv6, link-local, you name it. We could use the name that you can assign to the instance, however then we have to deal with problems that it might characters that the various SIP service providers out there don't like and that might actually not be allowed according to RFC. It would turn this into a new problem area, especially because everyone wants to play with such settings and try out Japanese characters or just invisible spaces! Plus it makes the packet longer, getting us closer to the magic UDP packet size. If you want to separate the traffic for a specific trunk, we have the feature to turn PCAP on for that trunk, which nicely puts the packets to gather for you into one PCAP file (next version will even have precision time stamps). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.