I don’t understand why this would be needed. The bind statements for the dial peers would be done on the tenant. The SIP phones should use the bind statements on the global configuration under voice service voip.
Remove this from voice service voip.
localhost dns:sip.bluetelecoms.com
And attach the tenant to the inbound dial peer as well. On the topic of inbound dial peer I would recommend you to use a more specific match criteria than incoming called number. The recommendation is to use information in the VIA header.
The previous shared document outlines details on this.
Given that your version of IOS is quite old and outdated I would also recommend you to upgrade it. If you want to keep using traditional licenses the last version you could use is 16.9. Otherwise you should be able to go with 17.3.4 that we are currently standardised on at my work. This requires Smart Licensing FYI.
I’ll post an example later today on how to use VIA header to match inbound dial peer.
Yes it would be in the incoming invite. It’s one of the mandatory SIP headers. Basically you match on the information that you get in the VIA header, usually this is one IP or a network of IPs depending upon what your service provider sends to you.
Example of how to match on IP addresses in VIA header.
voice class uri PSTN sip host ipv4:<ITSP SBC IP 1> host ipv4:<ITSP SBC IP 2> ! dial-peer voice 4 voip description Incoming Dial Peer from PSTN incoming uri via PSTN
There are other options that can be used in the voice class uri, those are covered in the before linked to document.
I think that you might need to create another inbound dial peer that matches on the network address of your phones with the inside network as it’s bind statements for the phone to be able to make the call.
