Tailored negotiations with Telefônica Brazil

[Angelo Delphini (Professor Delphini)]

Good evening Kaian! All good with the peace of your smile?

Please take a look at the image below:

This image shows four important points for the perfect connection with Telefônica Brazil. They are:
=> From: sip:1130X...@10.255.240.111;tag=f0c2979219 // this is the A number, we are required to send it this way;
=> To: sip:996X...@10.155.240.11 // this is the B number.
=> Contact: sip:1130X...@10.12.94.194 // this is the IP that Telefônica provided for the circuit;
=> P-Asserted-Identity: sip:1130X...@10.255.240.111 // this is required to be sent this way to the challenger.

This is working correctly with a clean FreePBX 17 server.

 Now take a look at the next image, with a circuit from the same operator (Telefônica Brazil) but showing the information for these four fields outside of the required standard.

  

Question!!!???

How can I change:
=> Contact:
=> P-Asserted-Identity:

To match the operator’s standard, as it should be:
=> Contact: sip:1130X...@10.12.94.194;
=> P-Asserted-Identity: sip:1130X...@10.255.240.111.

Important information: the second image is a FreePBX 17 as a retailAccount in I::VOZ Provider.

-- 

Atenciosamente / Best regards / Saludos,

Angelo Delphini | Arquiteto de Soluções em Telecomunicações | Head de Treinamentos

Telemóvel | WhatsApp: +55 (11) 9 4418 2371

   _
  °v°         Asterisk Libre
 /(_)\  http://www.asterisklibre.org/
  ^ ^
 Seja livre, use Asterisk Puro!
 --------------------------
 Open Source \o/\o/ - Milhares de mentes abertas não podem estar enganadas!

Pense bem antes de imprimir
Você está preservando a natureza, as árvores agradecem!

[Kaian]

Hi!

There are several ways to change presentation (PAI header). Most common one is using Numeric Transformations, which contains rules to transform from Carrier format to E.164 (the format used internally in invozprovider) and vice versa.

If this is an Outbound external call through a Carrier, you can create a Transformation Rule and edit Caller Out Transformations rules to add a prefix (Or multiple rules, one to remove +55 and another to add 1130).

About Contact header, there is no way to modify this in ivozprovider and as far as I know that should not be changed according to SIP RFC. There are Record-Route headers present in the dialog, so Contact fields should not even been considered by the Carrier.

Best regards,

[Angelo Delphini (Professor Delphini)]

 Kain, thank you for the response. Unfortunately, it is a problem here in Brazil, but don't worry, I've already overcome that obstacle by creating explicit rules in FreePBX and including the IP in question in the RTPENGINE.CONF. Thank you very much! I really appreciate your support!