Re: [SR-Users] Problem with auth_ephemeral and parse_uri(): bad port in uri

Hi Henning, I just tried the default IETF format ("1") but I get the same error from Kamailio: Jan 24 13:57:59 enswitch43 /sbin/kamailio[432531]: DEBUG: {1 988 REGISTER fm2l7am7uggc2gc7jslpfj} sanity [sanity.c:817]: check_parse_uris(): parsing From URI Jan 24 13:57:59 enswitch43 /sbin/kamailio[432531]: DEBUG: {1 988 REGISTER fm2l7am7uggc2gc7jslpfj} <core> [core/parser/parse_uri.c:1296]: parse_uri(): bad port in uri (error at char 2 in state 2) parsed: <sip:1643036115:35189>(20) /<sip:1643036115:3518929@192.168.2.99> (35) Jan 24 13:57:59 enswitch43 /sbin/kamailio[432531]: WARNING: {1 988 REGISTER fm2l7am7uggc2gc7jslpfj} sanity [sanity.c:820]: check_parse_uris(): failed to parse From uri In this case 35189 is the user and 1643036115 is the timestamp. REGISTER sip:192.168.2.99 SIP/2.0 Via: SIP/2.0/WSS 192.0.2.155;branch=z9hG4bK4638021 Max-Forwards: 70 To: "3518929" <sip:1643036115:3518929@192.168.2.99> From: "3518929" <sip:1643036115:3518929@192.168.2.99>;tag=puibbfcnui Call-ID: fm2l7am7uggc2gc7jslpfj CSeq: 988 REGISTER Contact: <sip:o4j2rcer@192.0.2.155;transport=wss>;reg-id=1;+sip.instance="<urn:uuid:1058141a-a8eb-40c5-bd6b-50dd763a7b7e>";expires=300 Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER Supported: path, gruu, outbound User-Agent: Raspberry Phone (SipJS - 0.11.6) Content-Length: 0 Kamailio still treats the number after : as the port. On 3/1/2022 18:54, Henning Westerholt wrote: