[SR-Users] uri2dst: bad_uri

[Yuriy Gorlichenko]

Hello. We use 2 kamailio behind  load balanser that have domain name of our
system .
uac settings like this:

modparam("uac","restore_mode","none")
modparam("uac","reg_db_url", DBURL)
modparam("uac", "reg_db_table", "uacreg")
modparam("uac", "reg_timer_interval", 20)
modparam("uac", "reg_retry_interval", 10)
modparam("uac", "reg_contact_addr", "sip.service.com:5068")

modparam("uac","auth_realm_avp","$avp(s:realm)")
modparam("uac","auth_username_avp","$avp(s:uname)")
modparam("uac","auth_password_avp","$avp(s:passwd)")


We have a trouble with registering trunks at porvider. When UAC try to
register trunk We see fails like this:

tm [ut.h:272]: uri2dst2(): ERROR: uri2dst: bad_uri: sip.service.com
ERROR: tm [uac.c:266]: t_uac_prepare(): t_uac: no socket found
ERROR: uac [uac_reg.c:746]: uac_reg_update(): failed to send request for
[TRUNKNAME]

What we try:
advertised_address=sip.service.com
alias=sip.service.com
alias=kam2.service.com
alias=Kam1.extern.ip.addr
alias=Kam2.extern.ip.addr
alias=load.balanser.ext.ipaddr

These settings not resolved our issue.

We have another trouble and think that it depended issues:

We can call to external numbers through trunks, but call very slow. (10-15
seconds), and some operators (LIKE AT&T dropped our calls to voicemail
systems and somethink like that)

Our question is how to successfully register providers at UAC with this
scheme. thanks for advices.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20141002/8b79a6b3/attachment.html>