Here is my Outbound trunk definition:
Here is the relevant Invite Header:
Why is that second From: string there, and why is it a variable substitution that hasn’t happened? The folks on the far end think it’s what the Access SBC is not happy with - anybody know why it is sending a second From: line?
Two From headers is indeed a problem and violates the RFCs.
This is a fairly old system; is this the first attempt with this trunk? Or, had it been working and suddenly stopped?
I am guessing that some custom dialplan is responsible. On my systems,
grep -i calleridstring /etc/asterisk/*.conf
The Asterisk log for a failing call should give you a clue as to where it is being used.
Sure did - Thanks for the suggestion - fixed it!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.