[Spce-user] New install cannot register subscribers
Oren Yehezkely
orenyny at gmail.com
Mon Aug 5 02:56:53 EDT 2013
Lorenzo,
I hope you had the chance to get some coffee before reading my reply.
network.yml file does not look correct to me but i am not 100% how it
should look.
Obviously the installation did not work well, and I wonder how can it be.
Obviously when I saw the amount of scripts being installed and later
updated, i wondered how could it be that it is done with no error.
I hope that someone here is going to take a look at this to prevent errors
in the future.
What should I correct in this file? Should I reinstall the whole thing
again?
Thanks,
Oren
root at sipwise:/etc/ngcp-config# vi network.yml
---
hosts:
self:
interfaces:
- lo
lo:
ip: 127.0.0.1
netmask: 255.255.255.0
shared_ip: []
shared_v6ip: []
type:
- sip_int
- ha_int
- web_ext
- sip_ext
- rtp_ext
- web_int
v6ip: '::1'
role:
- proxy
- lb
- mgmt
On Mon, Aug 5, 2013 at 2:27 AM, Lorenzo Mangani
<lorenzo.mangani at gmail.com>wrote:
> Oren,
>
> It appears your Bria is sending REGISTRATIONS and getting zero replies.
> This suggests the system is not listening on the .246 but actually on the
> .24 address (as seen in the keep alives being answered), which would be the
> result of a network misconfiguration of the NGCP in my opinion, of course
> this could be wrong of course due to the fact i'm answering this before my
> coffee :) Please check the configuration in /etc/ngcp-config/network.yml
> and validate what you configured this system with - if needed, make changes
> and apply them according to the HandBook procedures for normal
> configuration, or share more details if in doubt.
>
> Best.
>
> Lorenzo Mangani
>
> HOMER DEV TEAM
> QXIP - Capture Engineering
>
> US: +17737475014
> NL: +31858880841
> SKYPE: +990009369991479725
> INUM: +883510001822925
> SIP: lorenzo at 6num.net
>
>
> On Mon, Aug 5, 2013 at 7:54 AM, Oren Yehezkely <orenyny at gmail.com> wrote:
>
>> Lorenzo,
>>
>> Thanks for your reply again.
>>
>> Please see attached text file with the capture. Original IP addresses
>> were replaced, but you can still see the ending sometimes it is 24 (which
>> is incorrect)
>> and sometimes it is the correct 246,
>>
>> Where can i find the network.yml file and how do you think that the
>> misconfiguration could have happened.
>>
>> Thanks,
>>
>> Oren
>>
>>
>> On Sun, Aug 4, 2013 at 6:57 PM, Lorenzo Mangani <
>> lorenzo.mangani at gmail.com> wrote:
>>
>>> Oren,
>>>
>>> If the machine has the right address, I'd double check the network.yml
>>> configuration for errors.
>>> The messages you pasted are from sipsak - seeing the traces from a
>>> device will tell the story better about both issues.
>>> Start ngrep like you did above and restart the softclient to capture the
>>> REGISTER messages for this subscriber as well as the replies from the NGCP.
>>>
>>> Best.
>>>
>>> Lorenzo Mangani
>>>
>>> HOMER DEV TEAM
>>> QXIP - Capture Engineering
>>>
>>>
>>> On Mon, Aug 5, 2013 at 12:08 AM, Oren Yehezkely <orenyny at gmail.com>wrote:
>>>
>>>> Lorenzo,
>>>>
>>>> Thanks for your reply.
>>>> All the IP addresses in the sample below are truncated. The address
>>>> ends with 24 instead of 246.
>>>> Not sure where I could be mistaken since the machine does have the
>>>> correct address. Seems more like a bug in one of the scripts, I guess.
>>>>
>>>> I a m not sure how to capture the traffic on the client side but I
>>>> tried with 2 different soft phones in a network tha has other SIP devices
>>>> working.
>>>>
>>>> Thanks,
>>>>
>>>> Oren
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Aug 4, 2013, at 4:44 PM, Lorenzo Mangani <lorenzo.mangani at gmail.com>
>>>> wrote:
>>>>
>>>> Oren,
>>>>
>>>> Those are just keep-alive messages and unrelated to your case. Could
>>>> you capture the SIP output of the actual device trying to REGISTER and the
>>>> resulting (failure?) messages sent back from the NGCP in order to make some
>>>> suggestions as of the problem? Also where did you see the address getting
>>>> truncated? You might be suffering from misconfiguration somewhere.
>>>>
>>>> Best
>>>>
>>>> Lorenzo Mangani
>>>>
>>>> HOMER DEV TEAM
>>>> QXIP - Capture Engineering
>>>>
>>>>
>>>> On Sun, Aug 4, 2013 at 8:57 PM, Oren Yehezkely <orenyny at gmail.com>wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I just installed a new server. Everything seems to work fine so far. I
>>>>> am able to reach the server using IP and host name.
>>>>>
>>>>> However no matter what I do, I cannot register any SIP device.
>>>>>
>>>>> I have tried creating 2 domains one with the host name and one with
>>>>> the IP address, none have worked.
>>>>>
>>>>> I have found about ngrep-sip by searching this list for similar issues
>>>>> and looked at the output.
>>>>>
>>>>> The only thing I have noticed is that in some messages the IP address
>>>>> of the server is truncated.
>>>>> So, assuming that the correct IP address (this is just an example, the
>>>>> correct IP address is an external IP) is 192.168.0.246.
>>>>> A message will show the IP address as 192.168.0.24 (note the missing 6
>>>>> at the end.
>>>>>
>>>>> Messages are below(I revised the actual IP address). Is this an
>>>>> expected behavior?
>>>>> If so, can you tell why I cannot register? I have no additional
>>>>> firewall.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Oren
>>>>>
>>>>> U 2013/08/04 14:47:45.246025 127.0.0.1:5062 -> 127.0.0.1:5060
>>>>> SIP/2.0 200 Alive'
>>>>> Record-Route: <sip:127.0.0.1;lr=on;ftag=3319431d;ngcplb=yes;socket=udp:
>>>>> 127.0.0.1:5060>'
>>>>> Via: SIP/2.0/UDP
>>>>> 127.0.0.1;branch=z9hG4bKe92c.17c5ccea973d4532a15a59c2f07c0ba3.0'
>>>>> Via: SIP/2.0/UDP 192.168.0.24:9676
>>>>> ;received=127.0.0.1;branch=z9hG4bK.6705ebfe;rport=9676;alias'
>>>>> From: sip:sipsak at 192.168.0.24:9676;tag=3319431d'
>>>>> To: sip:nagios at voip.sipwise.local
>>>>> ;tag=1d24a28a0bded6c40d31e6db8aab9ac6.678b'
>>>>> Call-ID: 857293597 at 192.168.0.24'
>>>>> CSeq: 1 OPTIONS'
>>>>> P-Out-Socket: udp:127.0.0.1:5060'
>>>>> Server: Sipwise NGCP Proxy 2.X'
>>>>> Content-Length: 0'
>>>>> '
>>>>>
>>>>> #
>>>>> U 2013/08/04 14:47:45.246181 127.0.0.1:5060 -> 127.0.0.1:9676
>>>>> SIP/2.0 100 Trying'
>>>>> Via: SIP/2.0/UDP 192.168.0.24:9676
>>>>> ;received=127.0.0.1;branch=z9hG4bK.6705ebfe;rport=9676;alias'
>>>>> From: sip:sipsak at 192.168.0.24:9676;tag=3319431d'
>>>>> To: sip:nagios at voip.sipwise.local'
>>>>> Call-ID: 857293597 at 192.168.0.24'
>>>>> CSeq: 1 OPTIONS'
>>>>> Server: Sipwise NGCP Proxy 2.X'
>>>>> Content-Length: 0'
>>>>> '
>>>>>
>>>>> #
>>>>> U 2013/08/04 14:47:45.246303 127.0.0.1:5060 -> 127.0.0.1:9676
>>>>> SIP/2.0 200 Alive'
>>>>> Record-Route: <sip:127.0.0.1;lr=on;ftag=3319431d;ngcplb=yes;socket=udp:
>>>>> 127.0.0.1:5060>'
>>>>> Via: SIP/2.0/UDP 192.168.0.24:9676
>>>>> ;received=127.0.0.1;branch=z9hG4bK.6705ebfe;rport=9676;alias'
>>>>> From: sip:sipsak at 192.168.0.24:9676;tag=3319431d'
>>>>> To: sip:nagios at voip.sipwise.local
>>>>> ;tag=1d24a28a0bded6c40d31e6db8aab9ac6.678b'
>>>>> Call-ID: 857293597 at 192.168.0.24'
>>>>> CSeq: 1 OPTIONS'
>>>>> Server: Sipwise NGCP Proxy 2.X'
>>>>> Content-Length: 0'
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> http://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/20130805/60c66d67/attachment-0001.html>
More information about the Spce-user
mailing list