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