[Spce-user] External peers registration
Daniel Grotti
dgrotti at sipwise.com
Fri Feb 15 09:29:25 EST 2019
It's hard to say with just this. It does not seem to be an issue.
It's better to ask your provider why it is not responding, so he can
tell you what's wrong with the REGISTER.
--
Daniel Grotti
Head of Customer Support Sipwise GmbH
e: dgrotti at sipwise.com Europaring F15
t: +43(0)130120332 A-2345 Brunn Am Gebirge
w: www.sipwise.com FN: 305595f FG: LG Wiener Neustadt
On 2/15/19 3:26 PM, rleone.soluzioni at libero.it wrote:
>
> i'v configured remote autenthication section and checked peer auth
> register.
>
> i can see REGISTER but not receive answer (i receive 408 timout error)
>
> with previous version with same parameters is ok.
>
> What mean:
>
> /#7f67aa84a700/32199] [update_uac_reply, trans_layer.cpp:2052] INFO: />>>/disable blacklisting: remote UA (127.0.0.1/5060) did reply/
>
> maybe tis is the problem
>
>
>
>> Il 15 febbraio 2019 alle 15.18 Daniel Grotti <dgrotti at sipwise.com> ha
>> scritto:
>>
>> Have you configured also the Remote authentication section in the
>> peer's preferences?
>> Have you set peer_auth_register there?
>>
>> Please make sure you have done all this and then:
>>
>> - run "sngrep"
>> - restart sbc
>>
>>
>> you should see a REGISTER message going out to your provider.
>>
>>
>> --
>> Daniel Grotti
>>
>> Head of Customer Support Sipwise GmbH
>> e:dgrotti at sipwise.com <mailto:dgrotti at sipwise.com> Europaring F15
>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>> w:www.sipwise.com <http://www.sipwise.com> FN: 305595f FG: LG Wiener Neustadt
>> On 2/15/19 3:12 PM, rleone.soluzioni at libero.it
>> <mailto:rleone.soluzioni at libero.it> wrote:
>>>
>>> Hi,
>>>
>>> in /etc/ngcp-sems/etc/reg_agent.conf:
>>>
>>>
>>> # IMPORTANT:
>>> # Only set "domain", "user" and "pwd", and leave "proxy" and
>>> "contact" EXACTLY
>>> # as is to make outbound registrations to work.
>>> #
>>> # Note that the "contact" parameter is specific to the Sipwise SPCE
>>> and does
>>> # not yet exist in the official sems.
>>>
>>> domain=xxx.xxx.xxx.xxx
>>> user=uservoip
>>> pwd=pwdvoip
>>> proxy=sip:127.0.0.1:5060
>>> contact=sip:xxx.xxx.xxx.xxx:5060
>>>
>>> #domain1=<your peer realm>
>>> #user1=<your peer user>
>>> #pwd1=<your peer password>
>>> #proxy1=sip:127.0.0.1:5060
>>> #contact1=sip:xxx.xxx.xxx.xxx:5060
>>>
>>>
>>> #domain2=<your peer realm>
>>> #user2=<your peer user>
>>> #pwd2=<your peer password>
>>> #proxy2=sip:127.0.0.1:5060
>>> #contact2=sip:xxx.xxx.xxx.xxx:5060
>>>
>>>
>>> # Up to 50 registrations are possible.
>>>
>>>
>>>
>>> tail -f /etc/ngcp-sems/etc/reg_agent.conf
>>>
>>> ...
>>>
>>> [#7f5cd6018700/5154] [update_uac_reply, trans_layer.cpp:2052] INFO:
>>> disable blacklisting: remote UA (127.0.0.1/5060) did reply
>>> [#7f5cd6018700] [update_uac_reply, trans_layer.cpp:2052] INFO:
>>> disable blacklisting: remote UA (127.0.0.1/5060) did reply
>>>
>>>
>>>> Il 15 febbraio 2019 alle 15.03 Daniel Grotti <dgrotti at sipwise.com>
>>>> <mailto:dgrotti at sipwise.com> ha scritto:
>>>>
>>>> Hi,
>>>> the second one is the correct one.
>>>> Try to use the second one, and then apply.
>>>> After that, what do you have in / etc/ngcp-sems/etc/reg_agent.conf ?
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Grotti
>>>>
>>>> Head of Customer Support Sipwise GmbH
>>>> e:dgrotti at sipwise.com <mailto:dgrotti at sipwise.com> Europaring F15
>>>> t: +43(0)130120332 A-2345 Brunn Am Gebirge
>>>> w:www.sipwise.com <http://www.sipwise.com> FN: 305595f FG: LG Wiener Neustadt
>>>> On 2/15/19 3:01 PM, rleone.soluzioni at libero.it
>>>> <mailto:rleone.soluzioni at libero.it> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Has anyone had the same issues with logging to external peers?
>>>>>
>>>>>
>>>>> if in
>>>>> /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.customtt.tt2
>>>>>
>>>>>
>>>>> domain=xxx.xxx.xxx.xxx
>>>>> user=uservoip
>>>>> pwd=passvoip
>>>>> #proxy=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% IF sip_adv_ips.size -%]
>>>>> #contact=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% ELSE -%]
>>>>> #contact=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% END -%]
>>>>>
>>>>> in /var/log/ngcp/sems.log :
>>>>>
>>>>> [#7fe28c899740] [main, sems.cpp:634] INFO: SEMS 1.6.0
>>>>> (x86_64/linux) started
>>>>>
>>>>> [#7fe27ae98700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>>
>>>>> [#7f404838b700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f404828a700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f4048189700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f401bfff700] [run, tcp_trsp.cpp:807] INFO: Started SIP server
>>>>> TCP transport on 127.0.0.1:5080[
>>>>>
>>>>> [#7fc2a9bdd700] [sendto, udp_trsp.cpp:179] ERROR:
>>>>> sendto(14;xxx.xxx.xxx.xxx:5060): Invalid argument
>>>>>
>>>>> [#7fc2a9bdd700] [send_request, trans_layer.cpp:1311] ERROR: Error
>>>>> from transport layer
>>>>>
>>>>> otherwise
>>>>>
>>>>> in
>>>>> /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.customtt.tt2 :
>>>>>
>>>>> domain=xxx.xxx.xxx.xxx
>>>>> user=uservoip
>>>>> pwd=passvoip
>>>>> proxy=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% IF sip_adv_ips.size -%]
>>>>> contact=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% ELSE -%]
>>>>> contact=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]
>>>>> [% END -%]
>>>>>
>>>>> in /var/log/ngcp/sems.log :
>>>>>
>>>>> [#7f4055ecf740] [XMLRPC2DIServer, XMLRPC2DI.cpp:384] INFO: IP =
>>>>> 127.0.0.1 port = 8090
>>>>> [#7f4055ecf740] [loadFile, AmConfigReader.cpp:82] WARNING: could
>>>>> not open configuration file
>>>>> '/etc/ngcp-sems/etc/cc_call_timer.conf': No such file or directory
>>>>> [#7f4055ecf740] [onLoad, CallTimer.cpp:81] INFO:
>>>>> cc_call_timerconfiguration file
>>>>> (/etc/ngcp-sems/etc/cc_call_timer.conf) not found, assuming
>>>>> default configuration is fine
>>>>> [#7f4055ecf740] [initMonitoring, AmSessionContainer.cpp:119] INFO:
>>>>> monitoring module not loaded, monitoring disabled
>>>>> [#7f4055ecf740] [main, sems.cpp:634] INFO: SEMS 1.6.0
>>>>> (x86_64/linux) started
>>>>> [#7f404848c700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f404838b700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f404828a700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f4048189700] [run, udp_trsp.cpp:312] INFO: Started SIP server
>>>>> UDP transport on 127.0.0.1:5080
>>>>> [#7f401bfff700] [run, tcp_trsp.cpp:807] INFO: Started SIP server
>>>>> TCP transport on 127.0.0.1:5080[
>>>>>
>>>>> #7f67aa84a700/32199] [update_uac_reply, trans_layer.cpp:2052]
>>>>> INFO: disable blacklisting: remote UA (127.0.0.1/5060) did reply
>>>>>
>>>>> [#7f67aa749700] [update_uac_reply, trans_layer.cpp:2052] INFO:
>>>>> disable blacklisting: remote UA (127.0.0.1/5060) did reply
>>>>>
>>>>>
>>>>> with both configurations the registration fails
>>>>>
>>>>> version in use 6.5.3
>>>>> with previous 5.x is ok
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190215/0b491b11/attachment-0001.html>
More information about the Spce-user
mailing list