24 Jan
2023
24 Jan
'23
9:37 a.m.
Hello,
to clarify a bit more on the original question: it is indeed allowed to
have a port in the To header URI, but it is not required to have a port
in the To header URI.
From that perspective, you can consider that you are "not forced" to set
a port in there, the SBC has to work with a To URI without port.
Usually the issue in such case is that they configured the SBC to use
the To URI for routing, which is a wrong approach, they must use R-URI
for routing.
Cheers,
Daniel
On 24.01.23 09:02, Henning Westerholt wrote:
Hello,
usually, you have a in the To header an URI, and this can of course contain a port:
SIP-URI = "sip:" [ userinfo ] hostport
uri-parameters [ headers ]
SIPS-URI = "sips:" [ userinfo ] hostport
uri-parameters [ headers ]
For more information refer to e.g. section 25 of RFC 3261.
Cheers,
Henning
-----Original Message-----
From: Olivier <oza.4h07(a)gmail.com>
Sent: Tuesday, January 24, 2023 8:22 AM
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] [SR-Users]: Port number in To: field
Hello,
While trunking with an Oracle SBC, I was lately required to include a port number in
INVITE To: field.
Would you qualify this as a "legal requirement" (according to SIP Standards) ?
Best regards
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email
to sr-users-leave(a)lists.kamailio.org
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 sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com