[Spce-user] Extra socket for subcriber
Serge Yuriev
me at nevian.org
Sun Jun 7 14:52:45 EDT 2015
Hello,
I've checked db_mode and it was 1.
After restarting proxy started using socket from path attribute.
btw I changed db_mode to 2 to periodic db sync but unfortunately seems that is only one-way sync to db: changes from DB are not reflected in proxy :(
For future reference: we can manage such w/o restarting proxy like (one-liner)
ngcp# /usr/sbin/ngcp-kamctl proxy ul add cucmuser@<domain> sip:cucmuser at 10.0.64.64:5060 0
\<sip:127.0.0.1:5060\;lr\;socket=sip:10.0.64.100:5060\>
Thank you for your support!
On 6 Jun 2015, at 17:46, Daniel Grotti <dgrotti at sipwise.com> wrote:
> Restarting proxy should load your changes in memory.
>
>
> On Jun 6, 2015 4:24 PM, Serge Yuriev <me at nevian.org> wrote:
>>
>> Hello,
>>
>> Need to check but I didn't changed this param from shipped config
>>
>> --
>> Serge via mobile
>>
>>> On 6 июня 2015 г., at 15:56, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>>
>>> Hi,
>>> which db_mode value do you have for usrloc ?
>>> Cause probably you need to restart proxy since memory still contain the old path.
>>>
>>> Daniel
>>>
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "Serge Yuriev" <me at nevian.org>
>>> To: spce-user at lists.sipwise.com
>>> Sent: Saturday, June 6, 2015 10:42:24 AM
>>> Subject: Re: [Spce-user] Extra socket for subcriber
>>>
>>> root at msk-vo-s-sbc1:/var/log/ngcp# ngcp-kamctl proxy ul show cucmuser at real.ip.x.142
>>>
>>> Contact:: <sip:cucmuser at 10.0.64.62:5060>;q=1;expires=-1433579632;flags=0x0;cflags=0x0;state=1;socket=<NUL>;methods=0xFFFFFFFF;user_agent=<SIP Router MI Server>;path=<<sip:127.0.0.1:5060;lr>>;reg-id=0
>>>
>>> root at msk-vo-s-sbc1:/var/log/ngcp# ngcp-kamctl proxy ul show cucmuser at 10.0.64.100
>>>
>>> Contact:: <sip:cucmuser at 10.0.64.64:5060>;q=1;expires=-1433579654;flags=0x0;cflags=0x0;state=1;socket=<NUL>;methods=0xFFFFFFFF;user_agent=<SIP Router MI Server>;path=<<sip:127.0.0.1:5060;lr>>;reg-id=0
>>>
>>> *************************** 2. row ***************************
>>> id: 13
>>> username: cucmuser
>>> domain: 83.143.192.142
>>> contact: sip:cucmuser at 10.0.64.62:5060
>>> received: NULL
>>> path: <sip:127.0.0.1:5060;lr;socket=sip:10.0.64.100:5060>
>>> expires: 1970-01-01 03:00:00
>>> q: 1.00
>>> callid: dfjrewr12386fd6-343 at kamailio.mi
>>> cseq: 1
>>> last_modified: 1970-01-01 03:00:00
>>> flags: 0
>>> cflags: 0
>>> user_agent: SIP Router MI Server
>>> socket: NULL
>>> methods: NULL
>>> ruid: ulcx-5531093a-ad3f-9
>>> reg_id: 0
>>> instance: NULL
>>> *************************** 6. row ***************************
>>> id: 247
>>> username: cucmuser
>>> domain: 10.0.64.100
>>> contact: sip:cucmuser at 10.0.64.64:5060
>>> received: NULL
>>> path: <sip:127.0.0.1:5060;lr;socket=sip:10.0.64.100:5060>
>>> expires: 1970-01-01 03:00:00
>>> q: 1.00
>>> callid: dfjrewr12386fd6-343 at kamailio.mi
>>> cseq: 1
>>> last_modified: 1970-01-01 03:00:00
>>> flags: 0
>>> cflags: 0
>>> user_agent: SIP Router MI Server
>>> socket: udp:127.0.0.1:5062
>>> methods: NULL
>>> ruid: ulcx-5571b07f-ac8c-2
>>> reg_id: 0
>>> instance: NULL
>>>
>>>
>>>> On 6 Jun 2015, at 11:18, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>>>
>>>> Sergey,
>>>> Run the SQL query with \G at the end.
>>>>
>>>> Also can you run the command ngcp-kamctl proxy ul show <pbxuser at domain>
>>>>
>>>>
>>>>
>>>>> On Jun 6, 2015 10:12 AM, Serge Yuriev <me at nevian.org> wrote:
>>>>>
>>>>> id username domain contact received path expires q callid cseq last_modified flags cflags user_agent socket methods ruid reg_id instance
>>>>> 247 cucmuser 10.0.64.100 sip:cucmuser at 10.0.64.64:5060 NULL <sip:127.0.0.1:5060;lr;socket=sip:10.0.64.100:5060> 1970-01-01 03:00:00 1.00 dfjrewr12386fd6-343 at kamailio.mi 1 1970-01-01 03:00:00 0 0 SIP Router MI Server udp:127.0.0.1:5062 NULL ulcx-5571b07f-ac8c-2 0 NULL
>>>>> 17 cucmuser 83.143.192.142 sip:cucmuser at 10.0.64.66:5060 NULL <sip:127.0.0.1:5060;lr;socket=sip:10.0.64.100:5060> 1970-01-01 03:00:00 1.00 dfjrewr12386fd6-343 at kamailio.mi 1 1970-01-01 03:00:00 0 0 SIP Router MI Server NULL NULL ulcx-5531093a-ad3f-d 0 NULL
>>>>>
>>>>> Path and socket fields for 247 modified by me.
>>>>>
>>>>>> On 6 Jun 2015, at 11:07, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>>>>>
>>>>>> Yeah,
>>>>>> Right, it should use and recover the socket from the location table.
>>>>>> Can you check the status of the registration of the PBX in the location table?
>>>>>>
>>>>>>
>>>>>>> On Jun 6, 2015 9:58 AM, Serge Yuriev <me at nevian.org> wrote:
>>>>>>>
>>>>>>> Daniel,
>>>>>>>
>>>>>>> I can’t find this setting for subscriber :(
>>>>>>> Looks like this only for peers
>>>>>>>
>>>>>>>> On 6 Jun 2015, at 10:55, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>>>>>>>
>>>>>>>> Sergey,
>>>>>>>> Did you set the outbound_socket in you PBX subscriber's preferences?
>>>>>>>>
>>>>>>>> Daniel
>>>>>>>>
>>>>>>>>> On Jun 6, 2015 8:10 AM, Serge Yuriev <me at nevian.org> wrote:
>>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I tried to manually fix path in location table in kamailio DB in following way
>>>>>>>>> <sip:127.0.0.1:5060;lr;socket=sip:10.0.64.100:5060>
>>>>>>>>>
>>>>>>>>> Nothing changes :(
>>>>>>>>>
>>>>>>>>>> On 5 Jun 2015, at 20:40, Jon Bonilla (Manwe) <manwe at sipdoc.net> wrote:
>>>>>>>>>>
>>>>>>>>>> El Fri, 05 Jun 2015 19:45:51 +0300
>>>>>>>>>> "Serge S. Yuriev" <me at nevian.org> escribió:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> We have multi-homed installation.
>>>>>>>>>>> Our default domain == external IP (x.x.x.x)
>>>>>>>>>>> Our PBX on network 10.0.64.0
>>>>>>>>>>> PBX registered as subscriber with permanent registration and trusted
>>>>>>>>>>> devices.
>>>>>>>>>>>
>>>>>>>>>>> We configured extra_socket 10.0.64.100 and extra RTP interface for this IP.
>>>>>>>>>>> Outbound calls from PBX works perfectly via extra IP.
>>>>>>>>>>> Incoming calls doesn't work as NGCP originates from default IP (x.x.x.x)
>>>>>>>>>>> and PBX denies such calls from unknown source.
>>>>>>>>>>>
>>>>>>>>>>> I made extra domain 10.0.64.100 and moved PBX records here but no luck -
>>>>>>>>>>> NGCP uses default IP :(
>>>>>>>>>>> How to manage this?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> NGCP will use the received socket as originating socket. This means that if you
>>>>>>>>>> received a SUBCRIBE in the extra socket, NGCP should use it when sending the
>>>>>>>>>> call to that subscriber too.
>>>>>>>>>>
>>>>>>>>>> In this case you have a permanent contact which means, I'm afraid, that you
>>>>>>>>>> don't have the socket information in the location table. I think you'll have
>>>>>>>>>> to manually add it in the DB.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> cheers,
>>>>>>>>>>
>>>>>>>>>> Jon
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Serge S. Yuriev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Spce-user mailing list
>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>
>>>>>>> --
>>>>>>> Serge S. Yuriev
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Spce-user mailing list
>>>>>>> Spce-user at lists.sipwise.com
>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>> --
>>>>> Serge S. Yuriev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>> --
>>> Serge S. Yuriev
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> 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
--
Serge S. Yuriev
More information about the Spce-user
mailing list