Scott1234 Posted May 13 Report Share Posted May 13 I have a need on a trunk where I need to define the from header as. <sip:{ext-ani}@{ip-address}> I used {ip-address} based on, Trunk Custom Headers (vodia.com) however, in PACP when using I see its replaced as <sip:123456789@{x-pre-adr}> with no IP data. just the include statement. Anyone have any thoughts? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 16 Report Share Posted May 16 The PBX uses some variables to insert the IP address pre-flight. This is because a SIP packet source address depends on the actual route which takes, so that you can use e.g. private IP addresses, VLAN IP addresses, VPN addresses, public addresses, IPv4 and IPv6 addresses all on the same server (many simple SIP servers don't do that). Anyhow as for the SIP trunk, there are other variables available, but they are not the same. As for trunk headers, the documentation shows what variables are available, but you can also see them listed on TRUNK log level 9 when you try this out. Quote Link to comment Share on other sites More sharing options...
Scott1234 Posted May 17 Author Report Share Posted May 17 9 hours ago, Vodia PBX said: The PBX uses some variables to insert the IP address pre-flight. This is because a SIP packet source address depends on the actual route which takes, so that you can use e.g. private IP addresses, VLAN IP addresses, VPN addresses, public addresses, IPv4 and IPv6 addresses all on the same server (many simple SIP servers don't do that). Anyhow as for the SIP trunk, there are other variables available, but they are not the same. As for trunk headers, the documentation shows what variables are available, but you can also see them listed on TRUNK log level 9 when you try this out. Not sure if I am following you. The PBX has direct WAN IP attached to interface, and I am using, {ip-address}. , Should this not replace with the WAN/Interface IP? Log level 9 looks like this, nothing further happens. The PCAP that shows up for this attempt has <sip:number@{x-pre-adr}> no IP data. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 18 Report Share Posted May 18 The problem is that the replacement of IP addresses was not envisioned so far... We'll add it to the next 69 build. As a workaround you'll have to "hardcode" the actual WAN address there for now. 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.