[Spce-user] Assistance with Peering

Mon Apr 17 18:01:28 EDT 2023

I contacted my provider on the registration issue I am having with the 
timeout.

They indicated my IP address is not being blocked, and if there was a 
problem with registration, I would either get a SIP 401, or SIP 403 
error. They then suggested a firewall on the system could be the cause.

Anyone think this is the case?

Thanks,

Trent

On 4/7/23 02:18, Marco Capetta via Spce-user wrote:
> Hi Trent,
>
> sorry for the late reply.
> I can confirm that the procedure can be done fully from the web 
> interface. In the past an additional step in configuration files was 
> necessary, but now not anymore.
> I retested the feature right now in your same version and I was not 
> able to reproduce the problem.
>
> I have the following setup in the peer:
>  * peer_auth_user: username
>  * peer_auth_pass: password
>  * peer_auth_realm: 9.9.9.9
> As soon as you enable the flag 'peer_auth_register' you should see in 
> sngrep tool the REGISTER message leaving SEMS (127.0.0.1:5080) and 
> reaching kamailio LB (127.0.0.1:5060).
> At the same time in SEMS verbose logs you should have something like:
>
> Apr  7 09:12:23 spce ngcp-sems[1035]: [#7f098aede700] [execute, 
> XMLRPC2DI.cpp:739] DEBUG:  XMLRPC2DI 
> 'db_reg_agent.createRegistration': function 'createRegistration'
> Apr  7 09:12:23 spce ngcp-sems[1035]: [#7f098aede700] [execute, 
> XMLRPC2DI.cpp:745] DEBUG:   params: <[45, 'username', 'password', 
> '9.9.9.9', 'sip:username at 192.168.1.88:5060;uuid=0;transport=udp', 
> 'username', 'peering']>
> Apr  7 09:12:23 spce ngcp-sems[1035]: [#7f098aede700] [invoke, 
> DBRegAgent.cpp:1536] DEBUG:  REGISTER: SEMS is about to Create a 
> registration for: object_id=<45>, type=<peering>, user=<username>, 
> realm=<9.9.9.9>
>
> Please double check that your system and all the services are up and 
> running.
> Try to update th esystem to the last version of the packages.
> If you did some manual customization in the system, please try to 
> remove it and repeat all the steps suggested in my last email.
>
> Regards
> Marco
>
>
>
> On 07/04/23 07:09, Walter Klomp via Spce-user wrote:
>> Perhaps try with an LTS version first before trying the cutting edge 11.2
>>
>> It’s not impossible for things to break in development
>>
>> On Fri, 7 Apr 2023 at 02:06, Trent Creekmore <trent at lindows.org> wrote:
>>
>>     Greetings,
>>
>>
>>     Anyone else have some idea on why there seems to be no attempt to
>>     connect to a peering provider?
>>
>>
>>     Thanks!
>>
>>
>>     Trent
>>
>>     On 4/2/23 14:39, Trent Creekmore wrote:
>>     > Hello.
>>     >
>>     >
>>     > Following the documentation:
>>     >
>>     >
>>     https://www.sipwise.com/doc/mr11.2.1/spce/ce/mr11.2.1/basicconfiguration/basicconfiguration.html#_creating_peering_servers
>>
>>     >
>>     >
>>     > I created a peering server as the guide shows to a provider.
>>     However,
>>     > after setting up the needed info and authentication details, I
>>     am not
>>     > seeing any indications of the system even trying to make any
>>     > connection/registration attempts.
>>     >
>>     > Since there is nothing in the web interface to check, I used
>>     sngrep
>>     > and watched for a while. Even going as far as rebooting the
>>     server and
>>     > still nothing.
>>     >
>>     > Any helpful tips on this?
>>     >
>>     > Thanks!
>>     >
>>     >
>>
>>     -- 
>>     Spce-user mailing list
>>     Spce-user at lists.sipwise.com
>>     http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>
>> -- 
>> Email header
>>
>> Company logo <https://scribe-mail.myrepublic.net/s2/5cp2v6ux> 	
>> Walter Klomp
>> Head of Voice Network
>>
>> Phone 	*+6568161120* <tel:+6568161120>
>> Phone 	*walter at myrepublic.net* <mailto:walter at myrepublic.net>
>>
>>
>> Beyond Work: VR Sim Racing, F1, Travel
>>
>> 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 
>> 319579
>> *www.myrepublic.net* <https://scribe-mail.myrepublic.net/s2/tidact0m>
>> *facebook-f * <https://scribe-mail.myrepublic.net/s2/xx0nq9qs> 
>> *instagram * <https://scribe-mail.myrepublic.net/s2/jrh0tzt9> 
>> *twitter * <https://scribe-mail.myrepublic.net/s2/jo8r4exb> 
>> *linkedin-in * <https://scribe-mail.myrepublic.net/s2/37lmu5mw>
>>
>>
>>
>> The information in this message is privileged and confidential. If 
>> you are not the intended recipient of this email, please don't read, 
>> copy, use, distribute or tell anyone about it; kindly destroy it and 
>> notify the sender by return email. Please advise immediately if you 
>> or your employer does not consent to email for messages of this kind. 
>> Any content that is not concerned with MyRepublic business reflects 
>> the views of the sender only and not those of MyRepublic.
>>
>>
>>
>> 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/>.
>>
>
> -- 
> *Marco Capetta *
> R&D Manager
>
> Sipwise GmbH | an ALE Company <http://www.sipwise.com>
> c/o ALE International – Austria Branch
> Saturn Tower
> Leonard-Bernstein-Straße 10
> 1220 Vienna, Austria
>
> Email: mcapetta at sipwise.com
> Website: www.sipwise.com <http://www.sipwise.com>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20230417/272a5de7/attachment-0001.html>