Benjamin Sartori

I tried using formatters in the target SIP device to solve this but never managed to make it work. I have read other posts in this forum about formatters not being applied, so I don't know if they are still a thing. My current solution is to keep invite_format = username and to create callflows with a single number, with a fixed custom SIP header setting P-Called-Party-ID={callflow_number} Not the most elegant solution but it should work.

Well PBX connector and devices have the same options for invite format. I don't really care about authentication methods, I need a username in the SIP invite URI and the called number in another header ('to' or 'P-Called-Party-ID')

Hello, I have been learning how to use (free) kazoo for a few weeks and there is one thing I cannot configure for incoming calls. I have registered a freePBX to one of the kazoo accounts' smart PBX as a SIP device. I can choose invite format for that device, but the SIP URI and "to" field are always the same (I mean both username or both e164, etc). What we need is SIP username in the URI and e164 in the "to" field. It is important for my company as it simplifies the routing of calls. Is there any easy way to get this ? If no where should I look in the code to modify it ? Thanks