[Spce-user] Problem with Peering Registration

Daniel Grotti dgrotti at sipwise.com
Tue Nov 13 07:06:47 EST 2018


Can you please paste here cat //etc/ngcp-sems/etc/reg_agent.conf ?



/Cheers,/

/

-- 
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/12/18 4:45 PM, EMMANUEL AFANG wrote:
> Yes,I checked the /peer_auth_register/ box. And I also checked the 
> Probing box in the Peer Servers section.
>
> Best Regards
>
> *Emmanuel Afang *
>
> *
> *
>
> Mobile +2347084280332
> Email: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com 
> <mailto:fang.emmanuel at gmail.com>_
>
> Skype: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>
>
>
>
> On Mon, Nov 12, 2018 at 4:40 PM Daniel Grotti <dgrotti at sipwise.com 
> <mailto:dgrotti at sipwise.com>> wrote:
>
>     Hi,
>     in your peering preferences, under Remote authentication, did you
>     set: peer_auth_register ?
>
>     -- 
>     Daniel Grotti
>     Head of Customer Support
>     Sipwise GmbH, Campus 21/Europaring F15
>     AT-2345 Brunn am Gebirge
>
>     Office: +43(0)130120332
>     Email:dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
>     Website:https://www.sipwise.com
>
>     On 11/12/18 4:31 PM, EMMANUEL AFANG wrote:
>>     Thanks for the response Daniel
>>     But that did not resolve it. I applied the setting and even
>>     rebooted server. Then captured again with tcpdump and sipwise is
>>     still not sending REGISTER.
>>     Any ideas what could be the problem?
>>
>>     Best Regards
>>
>>     *Emmanuel Afang *
>>
>>     *
>>     *
>>
>>     Mobile +2347084280332
>>     Email: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>     <mailto:fang.emmanuel at gmail.com>_
>>
>>     Skype: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>
>>
>>
>>
>>     On Mon, Nov 12, 2018 at 12:38 PM Daniel Grotti
>>     <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> wrote:
>>
>>         Hi,
>>         the problem is that you must comment out also
>>
>>         *
>>         **#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 -%]*
>>
>>
>>         so your code shouls look like
>>
>>         *
>>         **domain=**sipdomain.com <http://sipdomain.com>**
>>         **user=sipuser**
>>         **pwd=sippassword**
>>         **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 -%]**
>>         **
>>         *
>>
>>
>>         -- 
>>         Daniel Grotti
>>         Head of Customer Support
>>         Sipwise GmbH, Campus 21/Europaring F15
>>         AT-2345 Brunn am Gebirge
>>
>>         Office: +43(0)130120332
>>         Email:dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
>>         Website:https://www.sipwise.com
>>
>>         On 11/12/18 12:05 PM, EMMANUEL AFANG wrote:
>>>         Hi Daniel
>>>         You asked for content of:
>>>         //etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.customtt.tt2/
>>>
>>>         But I am sending you content of:
>>>         //etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2/
>>>
>>>             sipuser at sipwise:~# cat
>>>             /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2
>>>             [% argv.role='lb'; argv.type='sip_ext'; PROCESS
>>>             '/usr/lib/ngcp-ngcpcfg/get_all_shared_ips'; sip_ext_ips
>>>             = out -%]
>>>             [% IF !sip_ext_ips.size -%]
>>>             [% argv.role='lb'; argv.type='sip_ext'; PROCESS
>>>             '/usr/lib/ngcp-ngcpcfg/get_all_ips'; sip_ext_ips = out -%]
>>>             [% END -%]
>>>             [% argv.role='lb'; argv.type='sip_int'; PROCESS
>>>             '/usr/lib/ngcp-ngcpcfg/get_all_shared_ips'; sip_lb_ips =
>>>             out -%]
>>>             [% IF !sip_lb_ips.size -%]
>>>             [% argv.role='lb'; argv.type='sip_int'; PROCESS
>>>             '/usr/lib/ngcp-ngcpcfg/get_all_ips'; sip_lb_ips = out -%]
>>>             [% END -%]
>>>             [% argv.role='lb'; argv.type='sip_ext'; PROCESS
>>>             '/usr/lib/ngcp-ngcpcfg/get_all_adv_ips'; sip_adv_ips =
>>>             out -%]
>>>             # 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=sipdomain.com <http://sipdomain.com>
>>>             user=sipuser
>>>             pwd=sippassword
>>>             #domain=<your peer realm>
>>>             #user=<your peer user>
>>>             #pwd=<your peer password>
>>>             #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 -%]
>>>             #domain1=<your peer realm>
>>>             #user1=<your peer user>
>>>             #pwd1=<your peer password>
>>>             #proxy1=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]
>>>             [% IF sip_adv_ips.size -%]
>>>             #contact1=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]
>>>             [% ELSE -%]
>>>             #contact1=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]
>>>             [% END %]
>>>             #domain2=<your peer realm>
>>>             #user2=<your peer user>
>>>             #pwd2=<your peer password>
>>>             #proxy2=sip:[% sip_lb_ips.0 %]:[% kamailio.lb.port %]
>>>             [% IF sip_adv_ips.size -%]
>>>             #contact2=sip:[% sip_adv_ips.0 %]:[% kamailio.lb.port %]
>>>             [% ELSE -%]
>>>             #contact2=sip:[% sip_ext_ips.0 %]:[% kamailio.lb.port %]
>>>             [% END %]
>>>             # Up to 50 registrations are possible.
>>>
>>>
>>>
>>>
>>>         Best Regards
>>>
>>>         *Emmanuel Afang *
>>>
>>>         *
>>>         *
>>>
>>>         Mobile +2347084280332
>>>         Email: _a
>>>         <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>>         <mailto:fang.emmanuel at gmail.com>_
>>>
>>>         Skype: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>>
>>>
>>>
>>>
>>>         On Mon, Nov 12, 2018 at 11:56 AM Daniel Grotti
>>>         <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> wrote:
>>>
>>>             Hi,
>>>             please provide your
>>>             //etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.customtt.tt2
>>>
>>>
>>>             /
>>>
>>>             -- 
>>>             Daniel Grotti
>>>             Head of Customer Support
>>>             Sipwise GmbH, Campus 21/Europaring F15
>>>             AT-2345 Brunn am Gebirge
>>>
>>>             Office: +43(0)130120332
>>>             Email:dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
>>>             Website:https://www.sipwise.com
>>>
>>>             On 11/12/18 11:54 AM, EMMANUEL AFANG wrote:
>>>>             Thanks Daniel for your quick response.
>>>>             I did follow this guide, but sipwise does not seem to
>>>>             be sending out REGISTER message to Peer. I captured
>>>>             with tcpdump for more than an hour and not a single
>>>>             REGISTER message was sent from sipwise to peer. This is
>>>>             how I have it setup at the moment:
>>>>
>>>>                 Peer configured via sipwise GUI with
>>>>                 /peer_auth_user, peer_auth_pass /and
>>>>                 /peer_auth_realm/ all set and /peer_auth_register/
>>>>                 checked.
>>>>
>>>>                 Also set only the /domain/, /user /and /pwd /in the
>>>>                 //etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2
>>>>                 /file
>>>>
>>>>
>>>>             I tested in lab with softswitch that sends a 407
>>>>             Authentication Required when it receives an INVITE from
>>>>             sipwise and saw that sipwise successfully authenticates
>>>>             when SIP 407 is sent to it. The callflow for sipwise
>>>>             successful authentication is like this:
>>>>
>>>>                 sipwise sends INVITE ---->>  Provider
>>>>                 sipwise receives 407 Proxy Authentication Required
>>>>                 <<-----  Provider
>>>>                 sipwise sends INVITE (with credentials) ---->> Provider
>>>>
>>>>                 sipwise receives 180 Ringing <<-----  Provider
>>>>
>>>>
>>>>             So I see that indeed sipwise wants the SIP 407 sent to
>>>>             it, before it sends the credentials in an INVITE
>>>>             method. It never sends out the REGISTER method to the
>>>>             peer. Please how then can I achieve the callflow below:
>>>>
>>>>                 sipwise sends REGISTER ---->>  Provider
>>>>                 sipwise receives 401 Unauthorized <<----- Provider
>>>>                 sipwise sends REGISTER (w/credentials) ---->> Provider
>>>>
>>>>
>>>>             Will appreciate your feedback on this.
>>>>
>>>>             Best Regards
>>>>
>>>>             *Emmanuel Afang *
>>>>
>>>>             *
>>>>             *
>>>>
>>>>             Mobile +2347084280332
>>>>             Email: _a
>>>>             <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>>>             <mailto:fang.emmanuel at gmail.com>_
>>>>
>>>>             Skype: _a <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>>>
>>>>
>>>>
>>>>
>>>>             On Mon, Nov 12, 2018 at 10:41 AM Daniel Grotti
>>>>             <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> wrote:
>>>>
>>>>                 Yes,
>>>>                 that's possible. How to do that is written in the
>>>>                 handbook, under the peering section:
>>>>                 https://www.sipwise.com/doc/mr6.5.1/sppro/?_href=ar01s05.html#_registering_at_a_peering_server
>>>>
>>>>
>>>>
>>>>
>>>>                 -- 
>>>>                 Daniel Grotti
>>>>                 Head of Customer Support
>>>>                 Sipwise GmbH, Campus 21/Europaring F15
>>>>                 AT-2345 Brunn am Gebirge
>>>>
>>>>                 Office: +43(0)130120332
>>>>                 Email:dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
>>>>                 Website:https://www.sipwise.com
>>>>
>>>>                 On 11/12/18 10:35 AM, EMMANUEL AFANG wrote:
>>>>>                 Thanks Walter for your response.
>>>>>                 Please is it possible to set sipwise so it sends
>>>>>                 out REGISTER to peer first, like the callflow below:
>>>>>
>>>>>                     sipwise sends REGISTER ---->>  Provider
>>>>>                     sipwise receives 401 Unauthorized <<-----
>>>>>                     Provider
>>>>>                     sipwise sends REGISTER (w/credentials) ---->> 
>>>>>                     Provider
>>>>>
>>>>>
>>>>>                 Will appreciate your feedback on this.
>>>>>
>>>>>                 Best Regards
>>>>>
>>>>>                 *Emmanuel Afang *
>>>>>
>>>>>                 *
>>>>>                 *
>>>>>
>>>>>                 Mobile +2347084280332
>>>>>                 Email: _a
>>>>>                 <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>>>>                 <mailto:fang.emmanuel at gmail.com>_
>>>>>
>>>>>                 Skype: _a
>>>>>                 <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>                 On Sat, Nov 10, 2018 at 3:00 AM Walter Klomp
>>>>>                 <walter at myrepublic.net
>>>>>                 <mailto:walter at myrepublic.net>> wrote:
>>>>>
>>>>>                     Hi Emmanuel,
>>>>>
>>>>>                     This sounds more a provider issue than
>>>>>                     Sipwise. Sipwise will always authenticate with
>>>>>                     the credentials given a 407 comes back.
>>>>>
>>>>>                     Registration is usually only done to announce
>>>>>                     where inbound calls need to go to. (Having
>>>>>                     said that, sipwise should be sending
>>>>>                     registrations at least once an hour - did you
>>>>>                     check with sngrep or other sniffer that it’s
>>>>>                     indeed not sending anything, ever?)
>>>>>
>>>>>                     Yours sincerely,
>>>>>                     Walter
>>>>>
>>>>>                     On 9 Nov 2018, at 10:22 PM, EMMANUEL AFANG
>>>>>                     <afang.emmanuel at gmail.com
>>>>>                     <mailto:afang.emmanuel at gmail.com>> wrote:
>>>>>
>>>>>>                     (got a response from your server that I am
>>>>>>                     not a member but posting to members, so I
>>>>>>                     registered and re-posted)
>>>>>>                     Hi
>>>>>>                     I use the free edition of 3CX and I am able
>>>>>>                     to do Registrations with a Peering Partner
>>>>>>                     with the following settings (changed):
>>>>>>                     *IN 3CX This Works:*
>>>>>>
>>>>>>                         Registrar/Server/Gateway Hostname or IP 
>>>>>>                          == sytypeer.com <http://sytypeer.com/>>>>>>                          (port 5096)
>>>>>>                         Outbound Proxy       ==  1.1.1.244  (port
>>>>>>                         5096)
>>>>>>                         Type of Authentication     ==  Register
>>>>>>                         Authentication ID (aka SIP User ID)      
>>>>>>                          ==  11111uuuuu22222
>>>>>>                         Authentication Password           ==
>>>>>>                          11111ppppp22222
>>>>>>
>>>>>>
>>>>>>                     To configure the equivalence of this on
>>>>>>                     sipwise, I did this:
>>>>>>                     *IN SIPWISE CE GUI Peering Servers:*
>>>>>>
>>>>>>                         IP Address  == 1.1.1.244 (port 5096)
>>>>>>                         Probing   ==  (checked the box)
>>>>>>
>>>>>>                     *IN **SIPWISE CE **GUI Peering Server
>>>>>>                     Preferences:*
>>>>>>
>>>>>>                         peer_auth_user     == 11111uuuuu22222
>>>>>>                         peer_auth_pass     == 11111ppppp22222
>>>>>>                         peer_auth_realm    == sytypeer.com
>>>>>>                         <http://sytypeer.com/>
>>>>>>                         peer_auth_register ==  (checked the box)
>>>>>>
>>>>>>                     *IN SIPWISE
>>>>>>                     CE /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2*
>>>>>>
>>>>>>                         domain=sytypeer.com <http://sytypeer.com/>
>>>>>>                         user=11111uuuuu22222
>>>>>>                         pwd=11111ppppp22222
>>>>>>                         (the description says: 'Only set
>>>>>>                         "domain", "user" and "pwd", and leave
>>>>>>                         "proxy" and "contact" EXACTLY')
>>>>>>
>>>>>>
>>>>>>                     With the above SIPWISE settings, I still am
>>>>>>                     not able to REGISTER with partner. In fact,
>>>>>>                     SIPWISE is NOT sending REGISTRATIONS. The
>>>>>>                     callflow is like this:
>>>>>>                     sipwise sends INVITE ---->> Provider
>>>>>>                     sipwise receives 100 Trying <<----- Provider
>>>>>>                     sipwise receives 403 Forbidden <<----- Provider
>>>>>>                     sipwise sends ACK ---->> Provider
>>>>>>
>>>>>>                     What I am thinking is whether sipwise was
>>>>>>                     expecting to get a /407 Proxy Authentication
>>>>>>                     Required/ before it performs the
>>>>>>                     REGISTRATION, if so, how do I make sipwise
>>>>>>                     REGISTER with peer partner like 3CX does?
>>>>>>
>>>>>>                     Best Regards
>>>>>>
>>>>>>                     *Emmanuel Afang *
>>>>>>
>>>>>>                     *
>>>>>>                     *
>>>>>>
>>>>>>                     Mobile +2347084280332
>>>>>>                     Email: _a
>>>>>>                     <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>>>>>                     <mailto:fang.emmanuel at gmail.com>_
>>>>>>
>>>>>>                     Skype: _a
>>>>>>                     <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>                     On Fri, Nov 9, 2018 at 3:11 PM EMMANUEL AFANG
>>>>>>                     <afang.emmanuel at gmail.com
>>>>>>                     <mailto:afang.emmanuel at gmail.com>> wrote:
>>>>>>
>>>>>>                         Hi
>>>>>>                         I use the free edition of 3CX and I am
>>>>>>                         able to do Registrations with a Peering
>>>>>>                         Partner with the following settings
>>>>>>                         (changed):
>>>>>>                         *IN 3CX This Works:*
>>>>>>
>>>>>>                             Registrar/Server/Gateway Hostname or
>>>>>>                             IP   == sytypeer.com
>>>>>>                             <http://sytypeer.com>   (port 5096)
>>>>>>                             Outbound Proxy       ==  1.1.1.244
>>>>>>                              (port 5096)
>>>>>>                             Type of Authentication     ==  Register
>>>>>>                             Authentication ID (aka SIP User ID)  
>>>>>>                                  ==  11111uuuuu22222
>>>>>>                             Authentication Password           ==
>>>>>>                              11111ppppp22222
>>>>>>
>>>>>>
>>>>>>                         To configure the equivalence of this on
>>>>>>                         sipwise, I did this:
>>>>>>                         *IN SIPWISE CE GUI Peering Servers:*
>>>>>>
>>>>>>                             IP Address   == 1.1.1.244 (port 5096)
>>>>>>                             Probing     == (checked the box)
>>>>>>
>>>>>>                         *IN **SIPWISE CE **GUI Peering Server
>>>>>>                         Preferences:*
>>>>>>
>>>>>>                             peer_auth_user     == 11111uuuuu22222
>>>>>>                             peer_auth_pass     == 11111ppppp22222
>>>>>>                             peer_auth_realm    == sytypeer.com
>>>>>>                             <http://sytypeer.com>
>>>>>>                             peer_auth_register ==  (checked the box)
>>>>>>
>>>>>>                         *IN SIPWISE
>>>>>>                         CE /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2*
>>>>>>
>>>>>>                             domain=sytypeer.com <http://sytypeer.com>
>>>>>>                             user=11111uuuuu22222
>>>>>>                             pwd=11111ppppp22222
>>>>>>                             (the description says: 'Only set
>>>>>>                             "domain", "user" and "pwd", and leave
>>>>>>                             "proxy" and "contact" EXACTLY')
>>>>>>
>>>>>>
>>>>>>                         With the above SIPWISE settings, I still
>>>>>>                         am not able to REGISTER with partner. In
>>>>>>                         fact, SIPWISE is NOT sending
>>>>>>                         REGISTRATIONS. The callflow is like this:
>>>>>>                         sipwise sends INVITE ---->> Provider
>>>>>>                         sipwise receives 100 Trying <<----- Provider
>>>>>>                         sipwise receives 403 Forbidden <<-----
>>>>>>                         Provider
>>>>>>                         sipwise sends ACK ---->> Provider
>>>>>>
>>>>>>                         What I am thinking is whether sipwise was
>>>>>>                         expecting to get a /407 Proxy
>>>>>>                         Authentication Required/ before it
>>>>>>                         performs the REGISTRATION, if so, how do
>>>>>>                         I make sipwise REGISTER with peer partner
>>>>>>                         like 3CX does?
>>>>>>
>>>>>>
>>>>>>                         Best Regards
>>>>>>
>>>>>>                         *Emmanuel Afang *
>>>>>>
>>>>>>                         *
>>>>>>                         *
>>>>>>
>>>>>>                         Mobile +2347084280332
>>>>>>                         Email: _a
>>>>>>                         <mailto:cuzomba at dial-mobile.com>fang.emmanuel at gmail.com
>>>>>>                         <mailto:fang.emmanuel at gmail.com>_
>>>>>>
>>>>>>                         Skype: _a
>>>>>>                         <mailto:cuzomba at dial-mobile.com>fang.emmanuel_
>>>>>>
>>>>>>
>>>>>>                     _______________________________________________
>>>>>>                     Spce-user mailing list
>>>>>>                     Spce-user at lists.sipwise.com
>>>>>>                     <mailto:Spce-user at lists.sipwise.com>
>>>>>>                     https://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>>                     The contents of this email and any attachments
>>>>>                     are confidential and may also be privileged.
>>>>>                     You must not disseminate the contents of this
>>>>>                     email and any attachments without permission
>>>>>                     of the sender. If you have received this email
>>>>>                     by mistake, please delete all copies and
>>>>>                     inform the sender immediately. You may refer
>>>>>                     to our company's Privacy Policy here
>>>>>                     <https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/>.
>>>>>
>>>>>
>>>>>                 _______________________________________________
>>>>>                 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/mailman/private/spce-user_lists.sipwise.com/attachments/20181113/3df728b7/attachment.html>


More information about the Spce-user mailing list