Asterisk 13.18.3 PJSIP. Wrong Port In Contact Header In Reply To REGISTER?
Hi List
I have been pondering over a problem to use an asterisk server behind an SBC unable to successfully handle registrations.
Now I observed something strange which I suspect might be a bug on the asterisk side.
The SBC originates is register from Port 6011 to Port 5060 on the Asterisk.
The Contact Header of the REGISTER contains:
Contact: user@SBC-IP:6011
The Asterisk is sending the 200 OK to back from it’s port 5060 to SBC-IP:6011 nothing wrong with it. But when I looked at the Contact Header, which indicates a successful ‘binding’ I see:
Contact: user@ASTERISK-IP:6011
It looks like the SBC discards this Contact header as invalid and returning the 200 OK without contact to the registering client, indicating an unsuccessful registration.
All other clients I have tried registering directly to asterisk seem to ignore this port and just accept the 200OK. Only our SBC causes this problem.
I have attempted rewrite_contact yes and no, both with the same result.
So from my point of view, Asterisk is putting the ‘remote’ port instead of it’s own SIP port into the Contact Header.
Can anyone confirm this is misbehavior be pjsip? Could this be a known bug? A quick google search did not return any hits.
Mit freundlichen Grüssen
-Benoît Panizzon-
—
I m p r o W a r e A G – Leiter Commerce Kunden
One thought on - Asterisk 13.18.3 PJSIP. Wrong Port In Contact Header In Reply To REGISTER?
The Contact header in the 200 OK should contain that of the remote side. If rewrite_contact is set to “yes” it would be the source IP address and port. If set to “no” it would be the URI provided in the REGISTER. The problem doesn’t ring any bells, but the version is old and my memory of the past fuzzy so it’s possible it was a problem and was subsequently fixed. I also haven’t seen anyone report this in recent times and haven’t seen it myself.