[Spce-user] New install

Leighton Brennan leightonbrennan at gmail.com
Sun May 8 16:00:37 EDT 2016


Hi Lorenzo
Appreciate you taking a look. See grep result below from spce. I have
sanitized the output and replaced the domain name witj voip.mydomain.ie and
the public IP's with 1.1.1.1 and 2.2.2.2
Any help much appreciated.

REGISTER sip:voip.mydomain.ie SIP/2.0
Via: SIP/2.0/UDP 192.168.88.250:56882
;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
Max-Forwards: 70
Contact: <sip:testuser1 at 192.168.88.250:56882
;rinstance=fe34752a02540f2b>;+sip.instance="<urn:uuid:2da18620-0c39-42c3-a1bb-ae11208d4dba>";reg-id=1
To: "testuser1"<sip:testuser1 at voip.mydomain.ie>
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
Expires: 900
Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, NOTIFY, OPTIONS, UPDATE,
PRACK, MESSAGE, SUBSCRIBE
Supported: outbound, path
User-Agent: Bria iOS release 3.6.3 stamp 33676
Content-Length: 0
REGISTER sip:voip.mydomain.ie SIP/2.0
Via: SIP/2.0/UDP
127.0.0.1;branch=z9hG4bKd913.7a739f79c970460e6bc684a842bce2c1.0
Via: SIP/2.0/UDP 192.168.88.250:56882
;rport=56882;received=2.2.2.2;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
Max-Forwards: 69
Contact: <sip:testuser1 at 192.168.88.250:56882
;rinstance=fe34752a02540f2b>;+sip.instance="<urn:uuid:2da18620-0c39-42c3-a1bb-ae11208d4dba>";reg-id=1
To: "testuser1"<sip:testuser1 at voip.mydomain.ie>
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
Expires: 900
Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, NOTIFY, OPTIONS, UPDATE,
PRACK, MESSAGE, SUBSCRIBE
Supported: outbound, path
User-Agent: Bria iOS release 3.6.3 stamp 33676
Content-Length: 0
P-NGCP-Src-Ip: 2.2.2.2
P-NGCP-Src-Port: 56882
P-NGCP-Src-Proto: udp
P-NGCP-Src-Af: 4
P-Sock-Info: udp:1.1.1.1:5060
P-NGCP-Src-Nat: 1
Path: <sip:lb at 127.0.0.1;lr;received=sip:2.2.2.2:56882;socket=sip:
1.1.1.1:5060>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
127.0.0.1;branch=z9hG4bKd913.7a739f79c970460e6bc684a842bce2c1.0
Via: SIP/2.0/UDP 192.168.88.250:56882
;rport=56882;received=2.2.2.2;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
To: "testuser1"<sip:testuser1 at voip.mydomain.ie>
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
P-Out-Socket: udp:1.1.1.1:5060
P-NGCP-Auth-IP: 2.2.2.2
P-NGCP-Auth-UA: Bria iOS release 3.6.3 stamp 33676
Server: Sipwise NGCP Proxy 4.X
Content-Length: 0
SIP/2.0 403 Domain not served here
Via: SIP/2.0/UDP
127.0.0.1;branch=z9hG4bKd913.7a739f79c970460e6bc684a842bce2c1.0
Via: SIP/2.0/UDP 192.168.88.250:56882
;rport=56882;received=2.2.2.2;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
To: "testuser1"<sip:testuser1 at voip.mydomain.ie
>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.c03a
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
P-Out-Socket: udp:1.1.1.1:5060
P-NGCP-Auth-IP: 2.2.2.2
P-NGCP-Auth-UA: Bria iOS release 3.6.3 stamp 33676
Server: Sipwise NGCP Proxy 4.X
Content-Length: 0
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.88.250:56882
;rport=56882;received=2.2.2.2;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
To: "testuser1"<sip:testuser1 at voip.mydomain.ie>
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
Server: Sipwise NGCP Proxy 4.X
Content-Length: 0
SIP/2.0 403 Domain not served here
Via: SIP/2.0/UDP 192.168.88.250:56882
;rport=56882;received=2.2.2.2;branch=z9hG4bK-524287-1---ce71e67f33f88f2f
To: "testuser1"<sip:testuser1 at voip.mydomain.ie
>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.c03a
From: "testuser1"<sip:testuser1 at voip.mydomain.ie>;tag=e7fb9027
Call-ID: MzI4YmM2MGRkMGVkYWFiOTJiMWY3OTFlYWE0NjNmZTQ
CSeq: 1 REGISTER
Server: Sipwise NGCP Proxy 4.X
Content-Length: 0
OPTIONS sip:nagios at voip.sipwise.local SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:8971;branch=z9hG4bK.09cce2f4;rport;alias
From: sip:sipsak at 1.1.1.1:8971;tag=3296965d
To: sip:nagios at voip.sipwise.local
Call-ID: 848729693 at 1.1.1.1
CSeq: 1 OPTIONS
Contact: sip:sipsak at 1.1.1.1:8971
Content-Length: 0
Max-Forwards: 70
User-Agent: sipsak 0.9.7pre
Accept: text/plain
OPTIONS sip:nagios at voip.sipwise.local SIP/2.0
Record-Route: <sip:127.0.0.1;lr=on;ftag=3296965d;ngcplb=yes;socket=udp:
127.0.0.1:5060>
Via: SIP/2.0/UDP
127.0.0.1;branch=z9hG4bK7b7e.fe203d4b425ef593790f997e066d90a8.0
Via: SIP/2.0/UDP 1.1.1.1:8971
;received=127.0.0.1;branch=z9hG4bK.09cce2f4;rport=8971;alias
From: sip:sipsak at 1.1.1.1:8971;tag=3296965d
To: sip:nagios at voip.sipwise.local
Call-ID: 848729693 at 1.1.1.1
CSeq: 1 OPTIONS
Contact: sip:sipsak at 1.1.1.1:8971
Content-Length: 0
Max-Forwards: 69
User-Agent: sipsak 0.9.7pre
Accept: text/plain
P-NGCP-Src-Ip: 127.0.0.1
P-NGCP-Src-Port: 8971
P-NGCP-Src-Proto: udp
P-NGCP-Src-Af: 4
P-Sock-Info: udp:127.0.0.1:5060

On Sun, May 8, 2016 at 9:54 AM, Lorenzo Mangani <lorenzo.mangani at gmail.com>
wrote:

> Hi Leighton,
>
> No matter what it seems, the REGISTER message carries a header causing
> this issue.
> If you share the REGISTER + response here sanitized we might be able to
> help you further,
>
>
> Kind Regards,
>
> Lorenzo Mangani
> *Managing Director and Core Dev*
>
> QXIP BV - Capture Engineering
> Amsterdam, The Netherlands
>
> Desk: +31 20 8080468 / +1 202-632-7227
> Mobile: +31 6 4603-2730
> Email: info at qxip.net
>
> Find our more about HOMER, PCAPTURE, CAPTAGENT and all our Services and
> Solutions at http://qxip.net
>
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential or
> legally privileged information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient, please contact
> the sender by reply e-mail and destroy all copies of this original message.
>
> On Sun, May 8, 2016 at 10:29 AM, Gmail <leightonbrennan at gmail.com> wrote:
>
>> Hi Jonathan
>> Thanks for the info.
>> I am using Bria xlite client on iPhone which I have used many times
>> before for other sip testing, all I have ever setup for other sip servers
>> is DNS/IP address of registrar server, username and password.
>>
>> The DNS record is correct as using sngrep I can see the register message
>> hit the spce server.
>>
>> Best Regards
>> Leighton Brennan
>>
>> On 8 May 2016, at 08:41, Jonathan Yue <jonathan.yue at turboitsolutions.com>
>> wrote:
>>
>> some sip clients have complex settings for a sip account - sip sever /
>> sip proxy / domain; some only need inputs of sip server, username &
>> passwords. For latter case, make sure you input the exact fqdm you set up
>> as the user account's domain on spce. that fqdm must REAL, which means it
>> has an A record on your dns server resolved to your spce server's IP.
>>
>> hope that helps.
>>
>> ------ Original Message ------
>> From: "Gmail" <leightonbrennan at gmail.com>
>> To: "Lorenzo Mangani" <lorenzo.mangani at gmail.com>
>> Cc: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
>> Sent: 2016-05-08 12:25:04 AM
>> Subject: Re: [Spce-user] New install
>>
>>
>> Hey Lorenzo
>> I probably should have a said sngrep seems to show the correct register
>> message user at sip:DNSdomain whe. Using the DNS domain and also user at sip:x.x.x.x
>> if I try using the IP address.
>> Although I don't see the 403 response going back out to the registering
>> client from sngrep.
>> Thanks
>>
>> Best Regards
>> Leighton Brennan
>>
>> On 7 May 2016, at 21:34, Lorenzo Mangani <lorenzo.mangani at gmail.com>
>> wrote:
>>
>> Hi,
>>
>> You might want to try running sngrep on the CE box, start the client and
>> see what your client is trying to register as when receiving the 403.
>> Most likely it will answer the question, or provide elements to make a
>> suggestion. Also try use the outbound proxy settings to doublecheck its not
>> a DNS/SRV issue.
>>
>> Kind Regards,
>>
>> Lorenzo Mangani
>> *Managing Director and Core Dev*
>>
>> QXIP BV - Capture Engineering
>> Amsterdam, The Netherlands
>>
>> Desk: +31 20 8080468 / +1 202-632-7227
>> Mobile: +31 6 4603-2730
>> Email: info at qxip.net
>>
>> Find our more about HOMER, PCAPTURE, CAPTAGENT and all our Services and
>> Solutions at http://qxip.net
>>
>> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
>> for the sole use of the intended recipient(s) and may contain confidential or
>> legally privileged information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient, please contact
>> the sender by reply e-mail and destroy all copies of this original message.
>>
>> On Sat, May 7, 2016 at 10:20 PM, Leighton Brennan <
>> leightonbrennan at gmail.com> wrote:
>>
>>> Hi list
>>> I am new to sip wise and want to set up a test SIPwise server.
>>> I have installed Debian 8 with basic installation(no desktop etc as
>>> outlined in the install guide) I then ran the NGCP installer for v4.3.1 and
>>> all appears to have installed correctly.
>>>
>>> I proceed to go through the basic config as outlined in the docs,
>>> created reseller, domain, contact, account and then subscriber.
>>> I assigned the domain, contact etc to the reseller that I set up,
>>> however when I try to register a SIP endpoint I get a 403 domain not served
>>> here. Initially I created a DNS domain so to ensure it wasn't a DNS problem
>>> I created a second domain with the IP address and assigned to the same
>>> reseller but still get the same error.
>>> I checked the SQL data and can see that the reseller, domains etc are
>>> all present. I can't seem to find a reason why the SIP registration is
>>> failing.
>>>
>>> I also tried running "ngcpcfg apply" to see if that would get it working
>>> but no joy.
>>>
>>> I have not created any peerings yet but I don't think these are required
>>> to test the subscriber registration.
>>>
>>> Any help would be appreciated.
>>>
>>> Leighton
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>>
>


-- 
Best Regards
Leighton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160508/a8f8d96a/attachment-0001.html>


More information about the Spce-user mailing list