Yes, I just learned that the Register method is not appropriate for
registering several "numbers" in just one trunk. Still need to learn a lot.


Olle, thank you, I'm going to read it.

Atenciosamente,


[image: photo] <https://www.techer.com.br/>
*Carlos Escalona*
IT - Development

  41 3073-0091 | R 1011
  www.techer.com.br



On Thu, Jan 19, 2023 at 12:08 PM Olle E. Johansson <[email protected]> wrote:

> The IETF GIN standard for SIP was developed for this use-case, and it’s
> part of SIPconnect from SIP forum.
>
> /O
>
> > On 19 Jan 2023, at 15:30, Alex Balashov <[email protected]>
> wrote:
> >
> > The proper place is the user part of the Request URI (R-URI).
> >
> >> On Jan 19, 2023, at 9:05 AM, Carlos Escalona <
> [email protected]> wrote:
> >>
> >> Hello all! I have a question. In my system we use a series of VoIP
> providers to receive external calls to our telephone numbers, for the same
> provider we have several registered numbers and we need our providers to
> send that information in some way, so far it does not seem that there is a
> common way to do it (report the number that was dialed by the person who
> made the call). From what I understand, SIP does not have a place for that
> information because there are no things like phone numbers in the
> specification, my question is, is there a correct place to send such
> information, or is it entirely up to each provider? (Now, the most common
> is to have in the RURI and To header, the id of the trunk registered in the
> uacreg table) I have seen a couple of options that seem to me the most
> “correct”: send the information in the To header or send in a custom header.
> >>
> >> I really appreciate any help you can provide.
> >>
> >> Atenciosamente,
> >>
> >>
> >> Carlos Escalona
> >> IT - Development
> >>  41 3073-0091 | R 1011  www.techer.com.br
> >>
> >> O conteúdo desta mensagem é confidencial. Se você não se encontra na
> lista de destinatários ou tenha recebido por engano, não a copie, imprima,
> envie, ou utilize, de qualquer forma, seu conteúdo. Neste caso, destrua a
> mensagem e, por favor, notifique o remetente.
> >> __________________________________________________________
> >> Kamailio - Users Mailing List - Non Commercial Discussions
> >> To unsubscribe send an email to [email protected]
> >> Important: keep the mailing list in the recipients, do not reply only
> to the sender!
> >> Edit mailing list options or unsubscribe:
> >
> > --
> > Alex Balashov
> > Principal Consultant
> > Evariste Systems LLC
> > Web: https://evaristesys.com
> > Tel: +1-706-510-6800
> >
> > __________________________________________________________
> > Kamailio - Users Mailing List - Non Commercial Discussions
> > To unsubscribe send an email to [email protected]
> > Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> > Edit mailing list options or unsubscribe:
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>

-- 
O conteúdo desta mensagem é confidencial. Se você não se encontra na lista 
de destinatários ou tenha recebido por engano, não a copie, imprima, envie, 
ou utilize, de qualquer forma, seu conteúdo. Neste caso, destrua a mensagem 
e, por favor, notifique o remetente.

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

Reply via email to