Multiple from headers in Invite causing problems with Access SBC

[GSnover]

Here is my Outbound trunk definition:

username=UserName
fromdomain=a1west.sipregistration.com
type=friend
trustrpid=yes
sendrpid=yes
secret=Squirel
qualify=yes
nat=no
host=a1west.sipregistration.com
dtmfmode=rfc2833
canreinvite=no

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?

Thanks!

[Stewart1 (Stewart)]

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
shows nothing.

The Asterisk log for a failing call should give you a clue as to where it is being used.

[GSnover]

Sure did - Thanks for the suggestion - fixed it!