[Spce-user] Peering two SPCE over TLS

Daniel Grotti dgrotti at sipwise.com
Tue Jan 20 07:03:21 EST 2015


Did you check the flag "peer_auth_register" in the web interface ?

Also, you can check the statu of the registration in table
kamailio.sems_registrations.


Daniel


On 01/20/2015 12:59 PM, Daniel Grotti wrote:
> If you check kamailio-lb you should see logs line like "b2bua outbound
> registration".
>
>
> Daniel
>
>
>
> On 01/20/2015 12:55 PM, H Yavari wrote:
>> Hi,
>> cat /etc/ngcp-sems/etc/reg_agent.conf output:
>>
>> domain=X.X.X.X (ip static)
>> user=100011
>> pwd=pincode100011
>> proxy=sip:127.0.0.1:5060
>> contact=sip:192.168.X.Z:5060 (ip internal)
>>
>> proxy and contact info applied automatically after "ngcpcfg apply".
>>
>> I checked subscriber 100011 in the peer server but not registered any
>> device for it.
>>
>>
>> Thanks for helps.
>>
>> Regards,
>> H. Yavari
>>
>>
>> ------------------------------------------------------------------------
>> *From:* Daniel Grotti <dgrotti at sipwise.com>
>> **
>> Hi,
>> did you commented out all the lines in
>> /etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2 ?
>>
>> 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 -%]
>>
>>
>> contact line is missing, you should see something like:
>>
>> cat /etc/ngcp-sems/etc/reg_agent.conf
>>
>> domain=ip_ext:static
>> user=100011
>> pwd=pincode100011
>> proxy=sip:127.0.0.1:5060
>> contact=sip:XX.XX.XX.XX:5060
>>
>>
>>
>> Daniel
>>
>>
>> On 01/19/2015 02:11 PM, H Yavari wrote:
>>>
>>>
>>> Hi,
>>> It is my scenario:
>>>
>>> CPE(#1)        <------------------------>    CPE(#2)
>>> ip_ext: dynamic                               ip_ext:static
>>>
>>> I want create a sip trunk between them.
>>> I defined a peer server in CPE#1 for communicating with CPE#2. I did
>>> below configurations too:
>>> (/etc/ngcp-config/templates/etc/ngcp-sems/etc/reg_agent.conf.tt2)
>>>
>>> domain=ip_ext:static
>>> user=100011
>>> pwd=pincode100011
>>> proxy=sip:127.0.0.1:5060
>>>
>>> But CPE#1 not registered in CPE#2.
>>>
>>> What is the best solution for trubking between 2 CPE?
>>>
>>>
>>> Thanks for helps.
>>>
>>> Regards,
>>> H. Yavari
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>> *From:* Daniel Grotti <dgrotti at sipwise.com> <mailto:dgrotti at sipwise.com>
>>>
>>>
>>> Hi,
>>> looks like the tcp connection got timeout.
>>> Are you sure to have the port you need opened (5060 tcp and 5061 tcp) ?
>>>
>>> Daniel
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> *From: *"H Yavari" <hyavari at rocketmail.com>
>>> <mailto:hyavari at rocketmail.com>
>>> *To: *"Daniel Grotti" <dgrotti at sipwise.com>
>>> <mailto:dgrotti at sipwise.com>, spce-user at lists.sipwise.com
>>> <mailto:spce-user at lists.sipwise.com>
>>> *Sent: *Sunday, January 18, 2015 8:43:42 AM
>>> *Subject: *Re: [Spce-user] Peering two SPCE over TLS
>>>
>>> Hi,
>>> I tested it with TCP and I received "ERROR: <core>
>>> [tcp_main.c:4422]: tcpconn_main_timeout(): connect Public IP of peer
>>> server :5060 failed (timeout)"
>>>
>>>
>>> Regards,
>>> H. Yavari
>>> ------------------------------------------------------------------------
>>> *From:* Daniel Grotti <dgrotti at sipwise.com> <mailto:dgrotti at sipwise.com>
>>>
>>>
>>> No, as long as the message its relay in TLS with no errors, there
>>> are no problems.
>>> I guess it fails for timeout, since you don't get any message on the
>>> peer side, isn't?
>>> Daniel
>>>
>>>
>>> On 17 Jan 2015 14:17, H Yavari <hyavari at rocketmail.com>
>>> <mailto:hyavari at rocketmail.com> wrote:
>>>
>>>     Hi,
>>>
>>>     Yes I checked, There isn't any error and I see "transport=tls" too.
>>>     I should define any thing on the other server?
>>>
>>>
>>>     Regards,
>>>     H. Yavari
>>>
>>>     ------------------------------------------------------------------------
>>>     *From:* Daniel Grotti <dgrotti at sipwise.com>
>>>     <mailto:dgrotti at sipwise.com>
>>>
>>>
>>>     Can you check in the LB log you see what's happening? Do you see
>>>     errors? Do you see its using TLS socket ?
>>>     Daniel
>>>
>>>
>>>     On 17 Jan 2015 13:35, H Yavari <hyavari at rocketmail.com>
>>>     <mailto:hyavari at rocketmail.com> wrote:
>>>
>>>         Hi,
>>>         I mean in the proxy-log, not any request received by peer
>>>         server. Yes I checked and TLS is enabled on 5061 port.
>>>
>>>         Regards,
>>>         H. Yavari
>>>
>>>         ------------------------------------------------------------------------
>>>         *From:* Daniel Grotti <dgrotti at sipwise.com>
>>>         <mailto:dgrotti at sipwise.com>
>>>
>>>
>>>         Hi,
>>>         What do you mean no message received on the peer?
>>>         Did you enable TLS on your server in config.yml?
>>>
>>>         What does the kamailio-lb.log say?
>>>
>>>         DanielOn 17 Jan 2015 13:08, H Yavari <hyavari at rocketmail.com
>>>         <mailto:hyavari at rocketmail.com>> wrote:
>>>         >
>>>         > Hi,
>>>         >
>>>         > I want to create a trunk between 2 CPE in the internet
>>>         over TLS, and only one of them has static ip address. I
>>>         checked config.yml too and TLS is enabled on both server.
>>>         > So I defined an peer server with TLS protocol over port
>>>         5061 in that server that has dynamic ip. But when I make a
>>>         call on this server, not any request received in the other
>>>         Server. (Everything is ok over UDP )
>>>         >
>>>         > How can I solve this ? Should I defined any peer on the
>>>         other Server?
>>>         >
>>>         >
>>>         >
>>>         > Regards,
>>>         > H. Yavari
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
>> 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
> 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/20150120/aceb720e/attachment.html>


More information about the Spce-user mailing list