SIP-URIs and call log data

[EkFudrek]

Hi!

I recently ran into the problem that one could not use the call log of some phones to call back.

All external numbers are in E.164 format (+49…) and the PJSIP stack uses the external IP to form the INVITE URI, like

<— Received SIP request (1250 bytes) from TCP:217.0.17.17:5060 —>
INVITE sip:+4922224466880@80.155.166.177:5060;transport=TCP;line=yittgix SIP/2.0
…

This URI also gets stored exactly this way in some phones when handed over to local phones. Snom phones store it so, but Yealink or Fanvil do not seem to do it this way. Using the call log subsequent calls from Snom phones fail, but not from the other ones.

It seems that at least Snom phones interpret a URI like sip:+4922224466880@80.155.166.177:5060 as a routable SIP-URI and contact the router (as shown by pcap traces) instead of the PBX. My current patch is to explicitly set the P-Asserted-Identity header with the IP of the PBX, as this is what seems to get used by the Snom phones.

Is that an issue one should generally be aware of, or is this only a very special case?

The other question is whether there is a more elegant way to deal with this.

[penguinpbx]

If you configure the outbound proxy settings on the phone to the same IP & port as your PBX, then does that force all calls (including callbacks) to go through the proxy (that you control and runs Asterisk ?) instead of the router ?

[EkFudrek]

I think, I checked that, but I’ll check it again…