2010/1/27 Iñaki Baz Castillo ibc@aliax.net:
El Miércoles, 27 de Enero de 2010, escribió:
2010/1/27 Iñaki Baz Castillo ibc@aliax.net:
El Miércoles, 27 de Enero de 2010, Jon Farmer escribió:
Hi
Does anyone know why I am getting
ERROR: parse_uri: bad host in uri (error at char
from this ( i hidden the domain and IP)
How does the domain look? To show it replace the letters but keep the symbols (as underscore and so).
Hi,
Sorry I am not entirely sure what you mean could you give me an example please.
Hi, please keep the thread in the maillist.
I just mean that, to keep your domain hidden, just change the letters but no the symbols. Example:
- Real domain: mycompany-cool-voip.com
- Showed domain: lalalaala-lolo-lili.com
-- Iñaki Baz Castillo ibc@aliax.net
Sorry about the wrong reply address, blame gmail :-)
Here you go
INVITE sip:01684299007@mydomain.net:5060 SIP/2.0. Via: SIP/2.0/UDP 192.168.20.240:5060;branch=z9hG4bK-d8754z-ed473d0ab724045f-1---d8754z-;rport. Max-Forwards: 70. Contact: sip:500@78.32.132.193:5060. To: sip:01684299007@mydomain.net:5060. From: "Michele "sip:500@mydomain.net:5060;tag=fd5b583a. Call-ID: NzU1MTZiMjZjZGM0ZTY5ZmFhMWRjNDlkNGQxZTZmODM.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO. Content-Type: application/sdp. User-Agent: 3CXPhoneSystem 7.0.4708.0. Authorization: Digest username="500",realm="mydomain.net",nonce="4b606dcc81900a95d9962d3c737cc570e624d409",uri="sip:01684299007@mydomain.net:5060",response="1ac466e73c744ed5936179152b5b27d4",algorithm=MD5. Content-Length: 278. . v=0. o=3cxPS 444025798656 5368709121 IN IP4 78.32.132.193. s=3cxPS Audio call. c=IN IP4 78.32.132.193. t=0 0. m=audio 9000 RTP/AVP 0 8 3 101. c=IN IP4 78.32.132.193. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:3 GSM/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv.
On 1/27/10 5:52 PM, Jon Farmer wrote:
2010/1/27 Iñaki Baz Castilloibc@aliax.net:
El Miércoles, 27 de Enero de 2010, escribió:
2010/1/27 Iñaki Baz Castilloibc@aliax.net:
El Miércoles, 27 de Enero de 2010, Jon Farmer escribió:
Hi
Does anyone know why I am getting
ERROR: parse_uri: bad host in uri (error at char
from this ( i hidden the domain and IP)
How does the domain look? To show it replace the letters but keep the symbols (as underscore and so).
Hi,
Sorry I am not entirely sure what you mean could you give me an example please.
Hi, please keep the thread in the maillist.
I just mean that, to keep your domain hidden, just change the letters but no the symbols. Example:
- Real domain: mycompany-cool-voip.com
- Showed domain: lalalaala-lolo-lili.com
-- Iñaki Baz Castilloibc@aliax.net
Sorry about the wrong reply address, blame gmail :-)
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Cheers, Daniel
Here you go
INVITE sip:01684299007@mydomain.net:5060 SIP/2.0. Via: SIP/2.0/UDP 192.168.20.240:5060;branch=z9hG4bK-d8754z-ed473d0ab724045f-1---d8754z-;rport. Max-Forwards: 70. Contact:sip:500@78.32.132.193:5060. To:sip:01684299007@mydomain.net:5060. From: "Michele "sip:500@mydomain.net:5060;tag=fd5b583a. Call-ID: NzU1MTZiMjZjZGM0ZTY5ZmFhMWRjNDlkNGQxZTZmODM.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO. Content-Type: application/sdp. User-Agent: 3CXPhoneSystem 7.0.4708.0. Authorization: Digest username="500",realm="mydomain.net",nonce="4b606dcc81900a95d9962d3c737cc570e624d409",uri="sip:01684299007@mydomain.net:5060",response="1ac466e73c744ed5936179152b5b27d4",algorithm=MD5. Content-Length: 278. . v=0. o=3cxPS 444025798656 5368709121 IN IP4 78.32.132.193. s=3cxPS Audio call. c=IN IP4 78.32.132.193. t=0 0. m=audio 9000 RTP/AVP 0 8 3 101. c=IN IP4 78.32.132.193. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:3 GSM/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv.
2010/1/27 Daniel-Constantin Mierla miconda@gmail.com:
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Ok well here is a little more info. I am using domain table so I can do virtual hosting. This has been working for months and suddenly INVITE's stop with this error yesterday. However the UA can still register successfully on the domain. Nothing has changed in the config. This is not affecting all domains only a handful and they all started to error yesterday.
2010/1/27 Daniel-Constantin Mierla miconda@gmail.com:
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Also I forgot to say I can use the domain successfully from my own phone. There error so far with Polycom and 3CX systems.
Hello,
On 1/27/10 6:13 PM, Jon Farmer wrote:
2010/1/27 Daniel-Constantin Mierlamiconda@gmail.com:
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Also I forgot to say I can use the domain successfully from my own phone. There error so far with Polycom and 3CX systems.
is this the only message you get?
ERROR: parse_uri: bad host in uri (error at char
It should print more details, unless there is an '\0' in the uri. For sure there is a wrong value loaded/computed somewhere in config.
Cheers, Daniel
On 27 January 2010 20:33, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
On 1/27/10 6:13 PM, Jon Farmer wrote:
2010/1/27 Daniel-Constantin Mierlamiconda@gmail.com:
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Also I forgot to say I can use the domain successfully from my own phone. There error so far with Polycom and 3CX systems.
is this the only message you get?
ERROR: parse_uri: bad host in uri (error at char
It should print more details, unless there is an '\0' in the uri. For sure there is a wrong value loaded/computed somewhere in config.
Here is the full error details from deamon.log
Jan 28 09:55:31 enrichser openser[23556]: ERROR: parse_uri: bad host in uri (error at char Jan 28 09:55:31 enrichser openser[23556]: ERROR: parse_sip_msg_uri: bad uri sip:07595729469@ Jan 28 09:55:31 enrichser openser[23556]: ERROR: new_t: uri invalid Jan 28 09:55:31 enrichser openser[23556]: ERROR: t_newtran: new_t failed
The URI would have been sip:07595729469@mydomain.net
On 1/28/10 10:58 AM, Jon Farmer wrote:
On 27 January 2010 20:33, Daniel-Constantin Mierlamiconda@gmail.com wrote:
Hello,
On 1/27/10 6:13 PM, Jon Farmer wrote:
2010/1/27 Daniel-Constantin Mierlamiconda@gmail.com:
the function is used in may places, it might be due to setting a new uri with wrong format, not specific to initial received message. If you load values from database or you compose them in config, check the input values.
Also I forgot to say I can use the domain successfully from my own phone. There error so far with Polycom and 3CX systems.
is this the only message you get?
ERROR: parse_uri: bad host in uri (error at char
It should print more details, unless there is an '\0' in the uri. For sure there is a wrong value loaded/computed somewhere in config.
Here is the full error details from deamon.log
Jan 28 09:55:31 enrichser openser[23556]: ERROR: parse_uri: bad host in uri (error at char
it is clear you have a '\0' in the new uri.
Jan 28 09:55:31 enrichser openser[23556]: ERROR: parse_sip_msg_uri: bad urisip:07595729469@ Jan 28 09:55:31 enrichser openser[23556]: ERROR: new_t: uri invalid Jan 28 09:55:31 enrichser openser[23556]: ERROR: t_newtran: new_t failed
The URI would have been sip:07595729469@mydomain.net
I guess this is what you receive, but what operations do you do in the config to update the uri? (location, loading from db, lcr, load balancing, etc ...)
Cheers, Daniel