[Spce-user] Cisco SPA112 Configuration for SipWise

Skyler skchopperguy at gmail.com
Fri Sep 9 23:48:27 EDT 2016 

Hi,

don't know what that rejection is. sorry. if you do figure this out 8t
would be great if you could share the solution with the list.

Have a good day!

--Skyler

On Sep 9, 2016 9:42 PM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:

> Thanks Skyler,
>
> I think the only option I don't have configured like yours is the packet
> size. I'll try that tomorrow. Could you spot anything amiss with the
> registration captures I sent through?
>
> I wonder if there's any detailed logging I can access to see why the call
> won't pass through?
>
> I'll try out some of the suggestions from the other replies too.
>
> 4:41 am I should get some sleep!
>
> Thanks once again - very good of you to help.
>
> Best regards,
>
> Paul.
>
> Sent from a DANECO device.
>
> On 10 Sep 2016, at 4:31 am, Skyler <skchopperguy at gmail.com> wrote:
>
> Hi Paul,
>
> I have all defaults except these:
>
> SIP
> RTP Parameters
> RTP Packet Size: 0.020
> NAT Support Parameters
> Handle VIA received: yes
> Insert VIA received: yes
> Handle VIA rport: yes
> Insert VIA rport: yes
>
> Line 1
> NAT Settings
> NAT Mapping Enable: yes
> NAT Keep Alive Enable: yes
>
> hope that helps.
>
> --Skyler
>
> On Sep 9, 2016 8:06 PM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:
>
>> Hello Skyler,
>>
>>
>>
>> I made some changes on the SPA112 under Voice --> SIP --> NAT Support
>> Parameters. I set 'Handle VIA received', 'Insert VIA received', 'Handle VIA
>> rport', and 'Insert VIA rport' all to 'yes' just out of curiosity and at
>> least now the external IP address seems to be correctly listed under
>> 'Registered Devices' on SipWise. Still no inbound calls however.
>>
>>
>>
>> I ran sngrep from Putty and noticed this when trying to dial in from my
>> mobile:
>>
>>
>>
>>
>>
>>   [ ] 2    OPTIONS    sipsak at 127.0.0.2:7043     nagios at voip.sipwise.local
>> 6     127.0.0.1:7043         127.0.0.1:5060
>>
>>   [ ] 3    INVITE     07xxxxxx261 at 194.xxx.xxx.1 44xxxxxxx273 at 109.xxx.xx.1
>> 14    109.xxx.xx.133:5060    xxx.xxx.xxx.19:5060    REJECTED
>>
>>   [ ] 4    INVITE     07xxxxxx261 at 194.xxx.xxx.1 sipsp#44xxxxxxx273 at sip.da
>> 6     127.0.0.1:5080         127.0.0.1:5060         REJECTED
>>
>>   [ ] 5    OPTIONS    sipsak at 127.0.0.2:7800     nagios at voip.sipwise.local
>> 6     127.0.0.1:7800         127.0.0.1:5060
>>
>>
>>
>> I suppose the REJECTED Call States are important.
>>
>>
>>
>> If I enable call forward to voicemail for the subscriber when
>> unavailable, the inbound call successfully routes to the voicemail system
>> and I can leave a message.
>>
>>
>>
>> Not sure if any of this information is relevant or helpful!
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Paul.
>>
>>
>>
>> --
>>
>>
>> *Paul R. Smith B.Sc. (Hons.)*
>>
>> Managing Director
>>
>> Data Network Consultants Limited
>>
>>
>>
>> *T:   *01207 750 550
>>
>> *W: *www.daneco.co.uk
>>
>>
>>
>> [image: DANECO Logo]
>>
>>
>>
>> *iNorthumberland's Fixed Wireless Access Partner - Superfast Wireless
>> Network Specialists.*
>>
>>
>>
>> DANECO is a trading name of Data Network Consultants Limited.
>>
>>
>>
>> Company Reg. No: 06769055
>> Registered in England and Wales.
>>
>>
>>
>> This email and its contents are confidential and intended for the
>> addressee only. It may not be disclosed to or used by anyone else nor may
>> it be copied in any way. Data Network Consultants Limited nor the sender
>> accepts any responsibility for viruses and it is the addressee's
>> responsibility to check attachments if any. Any opinions expressed in this
>> email are those of the sender and not necessarily those of Data Network
>> Consultants Limited. If received in error please contact the sender to
>> advise then delete from your system.
>>
>>
>>
>>
>>
>>
>> -----Original message-----
>> *From:* Paul Smith <paul.smith at daneco.co.uk>
>> *Sent:* Sat 10-09-2016 02:26
>> *Subject:* Re: [Spce-user] Cisco SPA112 Configuration for SipWise
>> *To:* Skyler <skchopperguy at gmail.com>;
>> *CC:* spce-user at lists.sipwise.com;
>>
>> Hello Skyler,
>>
>>
>>
>> Here's the first copy and paste from the SPA112 Register attempts - the
>> .19 address is my SipWise server and the .53 is my WAN IP address at the
>> adapter end:
>>
>>
>>
>> *///////////////////////////////// BEGIN
>> ///////////////////////////////////////////*
>>
>>
>>
>>
>>
>> REGISTER sip:xxx.daneco.co.uk SIP/2.0.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;branch=z9hG4bK-afa4f41c.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62066 REGISTER.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=3600.
>>
>> User-Agent: Cisco/SPA112-1.4.1(002).
>>
>> P-Station-Name:  ;mac=5067aef193c0; display=""; sn=CCQ1948117D.
>>
>> Content-Length: 0.
>>
>> Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
>>
>> Supported: replaces.
>>
>> .
>>
>>
>> ##
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:5060
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;rport=5060;r
>> eceived=xxx.xxx.xxx.53;branch=z9hG4bK-afa4f41c.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62066 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:5060
>>
>> SIP/2.0 401 Unauthorized.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;rport=5060;r
>> eceived=xxx.xxx.xxx.53;branch=z9hG4bK-afa4f41c.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=1d24a28a0bded6c40d31
>> e6db8aab9ac6.7082.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62066 REGISTER.
>>
>> WWW-Authenticate: Digest realm="xxx.daneco.co.uk",
>> nonce="V9Nd61fTXL/F5QuWQlq4X3A0yGY8uqx9".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ####
>>
>> U xxx.xxx.xxx.53:5060 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk SIP/2.0.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;branch=z9hG4bK-efb04e58.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62067 REGISTER.
>>
>> Max-Forwards: 70.
>>
>> Authorization: Digest username="44xxxxxxx273",realm="xxx.daneco.co.uk
>> ",nonce="V9Nd61fTXL/F5QuWQlq4X3A0yGY8uqx9",uri="sip:xxx.daneco.co.uk",alg
>> orithm=MD5,response="e89a87f0ba8f8ed964ed21a0dfdcaa99".
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=3600.
>>
>> User-Agent: Cisco/SPA112-1.4.1(002).
>>
>> P-Station-Name:  ;mac=5067aef193c0; display=""; sn=CCQ1948117D.
>>
>> Content-Length: 0.
>>
>> Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
>>
>> Supported: replaces.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:5060
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;rport=5060;r
>> eceived=xxx.xxx.xxx.53;branch=z9hG4bK-efb04e58.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62067 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:5060
>>
>> SIP/2.0 200 OK.
>>
>> Via: SIP/2.0/UDP 192.168.1.60:5060;rport=5060;r
>> eceived=xxx.xxx.xxx.53;branch=z9hG4bK-efb04e58.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=78baee0fa0651659o0.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk>;tag=1d24a28a0bded6c40d31
>> e6db8aab9ac6.294a.
>>
>> Call-ID: a5d2d225-224d8d74 at 192.168.1.60.
>>
>> CSeq: 62067 REGISTER.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=2714;received="
>> sip:xxx.xxx.xxx.53:5060".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>>
>> *///////////////////////////////// END
>> ///////////////////////////////////////////*
>>
>>
>>
>> This time, here is the Register attempt using Zoiper:
>>
>>
>>
>> *///////////////////////////////// BEGIN
>> ///////////////////////////////////////////*
>>
>>
>>
>>
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;branch=z9hG
>> 4bK-524287-1---e765160ff2244f3c;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.51:46849;rinstance=430fcd93ec973
>> 1c8;transport=UDP>.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 1 REGISTER.
>>
>> Expires: 60.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---e765160ff2244f3c;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 1 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 401 Unauthorized.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---e765160ff2244f3c;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.e6c8.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 1 REGISTER.
>>
>> WWW-Authenticate: Digest realm="xxx.daneco.co.uk",
>> nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ###
>>
>> U xxx.xxx.xxx.53:46849 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;branch=z9hG
>> 4bK-524287-1---272ad1d946bb85fb;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.51:46849;rinstance=430fcd93ec973
>> 1c8;transport=UDP>.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 2 REGISTER.
>>
>> Expires: 60.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Authorization: Digest username="44xxxxxxx273",realm="xxx.daneco.co.uk
>> ",nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu",uri="sip:xxx.daneco.co.uk;tran
>> sport=UDP",response="cacf965b924afd4b11efc8da7d649c95",algorithm=MD5.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---272ad1d946bb85fb;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 2 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 200 OK.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---272ad1d946bb85fb;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.0eb4.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 2 REGISTER.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=1994;received="sip:xxx.xxx.xxx.53:5060",
>> <sip:44xxxxxxx273 at 192.168.1.51:46849;rinstance=430fcd93ec973
>> 1c8;transport=UDP>;expires=60;received="sip:xxx.xxx.xxx.53:46849".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.53:46849 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;branch=z9hG
>> 4bK-524287-1---425efb31184f4d94;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.51:46849;rinstance=430fcd93ec973
>> 1c8;transport=UDP>;expires=0;received="sip:xxx.xxx.xxx.53:46849".
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 3 REGISTER.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Authorization: Digest username="44xxxxxxx273",realm="xxx.daneco.co.uk
>> ",nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu",uri="sip:xxx.daneco.co.uk;tran
>> sport=UDP",response="cacf965b924afd4b11efc8da7d649c95",algorithm=MD5.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ##
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---425efb31184f4d94;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 3 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 200 OK.
>>
>> Via: SIP/2.0/UDP 192.168.1.51:46849;received=xx
>> x.xxx.xxx.53;branch=z9hG4bK-524287-1---425efb31184f4d94;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.6d9d.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=a596987f.
>>
>> Call-ID: jYLwbp53jbA2FMEOorPY9Q...
>>
>> CSeq: 3 REGISTER.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=1994;received="
>> sip:xxx.xxx.xxx.53:5060".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ##
>>
>> U xxx.xxx.xxx.53:46849 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;branch=z9
>> hG4bK-524287-1---97834a4804611bf6;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at xxx.xxx.xxx.53:46849;transport=UDP;rinstan
>> ce=72db80700d9ac55b>.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 1 REGISTER.
>>
>> Expires: 60.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---97834a4804611bf6;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 1 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 401 Unauthorized.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---97834a4804611bf6;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.463d.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 1 REGISTER.
>>
>> WWW-Authenticate: Digest realm="xxx.daneco.co.uk",
>> nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu".
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.53:46849 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;branch=z9
>> hG4bK-524287-1---b0cf2ab4523fa986;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at xxx.xxx.xxx.53:46849;transport=UDP;rinstan
>> ce=72db80700d9ac55b>.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 2 REGISTER.
>>
>> Expires: 60.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Authorization: Digest username="44xxxxxxx273",realm="xxx.daneco.co.uk
>> ",nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu",uri="sip:xxx.daneco.co.uk;tran
>> sport=UDP",response="cacf965b924afd4b11efc8da7d649c95",algorithm=MD5.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---b0cf2ab4523fa986;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 2 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ###
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 200 OK.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---b0cf2ab4523fa986;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.8fb0.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 2 REGISTER.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=1994;received="sip:xxx.xxx.xxx.53:5060",
>> <sip:44xxxxxxx273 at xxx.xxx.xxx.53:46849;transport=UDP;rinstan
>> ce=72db80700d9ac55b>;expires=60.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> ####################################
>>
>> U xxx.xxx.xxx.53:46849 -> xxx.xxx.xxx.19:5060
>>
>> REGISTER sip:xxx.daneco.co.uk;transport=UDP SIP/2.0.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;branch=z9
>> hG4bK-524287-1---c64acd23d6325fa6;rport.
>>
>> Max-Forwards: 70.
>>
>> Contact: <sip:44xxxxxxx273 at xxx.xxx.xxx.53:46849;transport=UDP;rinstan
>> ce=72db80700d9ac55b>.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 3 REGISTER.
>>
>> Expires: 60.
>>
>> User-Agent: Zoiper rd0af4c2.
>>
>> Authorization: Digest username="44xxxxxxx273",realm="xxx.daneco.co.uk
>> ",nonce="V9NgvFfTX5DxcT9wsq6jyFtei2umdYUu",uri="sip:xxx.daneco.co.uk;tran
>> sport=UDP",response="cacf965b924afd4b11efc8da7d649c95",algorithm=MD5.
>>
>> Allow-Events: presence, kpml, talk.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 100 Trying.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---c64acd23d6325fa6;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 3 REGISTER.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>> #
>>
>> U xxx.xxx.xxx.19:5060 -> xxx.xxx.xxx.53:46849
>>
>> SIP/2.0 200 OK.
>>
>> Via: SIP/2.0/UDP xxx.xxx.xxx.53:46849;received=
>> xxx.xxx.xxx.53;branch=z9hG4bK-524287-1---c64acd23d6325fa6;rport=46849.
>>
>> To: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=1d24a2
>> 8a0bded6c40d31e6db8aab9ac6.a59e.
>>
>> From: <sip:44xxxxxxx273 at xxx.daneco.co.uk;transport=UDP>;tag=b558be15.
>>
>> Call-ID: ACXMskCp2k2Ma9VqPIrlpg...
>>
>> CSeq: 3 REGISTER.
>>
>> Contact: <sip:44xxxxxxx273 at 192.168.1.60:5060>;expires=1992;received="sip:xxx.xxx.xxx.53:5060",
>> <sip:44xxxxxxx273 at xxx.xxx.xxx.53:46849;transport=UDP;rinstan
>> ce=72db80700d9ac55b>;expires=60.
>>
>> Server: Sipwise NGCP Proxy 4.X.
>>
>> Content-Length: 0.
>>
>> .
>>
>>
>>
>> *///////////////////////////////// END
>> ///////////////////////////////////////////*
>>
>>
>>
>>
>>
>> I hope I haven't obscured useful information.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> Paul.
>>
>>
>>
>> --
>>
>>
>> *Paul R. Smith B.Sc. (Hons.)*
>>
>> Managing Director
>>
>> Data Network Consultants Limited
>>
>>
>>
>> *T:   *01207 750 550
>>
>> *W: *www.daneco.co.uk
>>
>>
>>
>> [image: DANECO Logo]
>>
>>
>>
>> *iNorthumberland's Fixed Wireless Access Partner - Superfast Wireless
>> Network Specialists.*
>>
>>
>>
>> DANECO is a trading name of Data Network Consultants Limited.
>>
>>
>>
>> Company Reg. No: 06769055
>> Registered in England and Wales.
>>
>>
>>
>> This email and its contents are confidential and intended for the
>> addressee only. It may not be disclosed to or used by anyone else nor may
>> it be copied in any way. Data Network Consultants Limited nor the sender
>> accepts any responsibility for viruses and it is the addressee's
>> responsibility to check attachments if any. Any opinions expressed in this
>> email are those of the sender and not necessarily those of Data Network
>> Consultants Limited. If received in error please contact the sender to
>> advise then delete from your system.
>>
>>
>>
>>
>>
>>
>> -----Original message-----
>> *From:* Skyler <skchopperguy at gmail.com>
>> *Sent:* Sat 10-09-2016 01:59
>> *Subject:* RE: [Spce-user] Cisco SPA112 Configuration for SipWise
>> *To:* Paul Smith <paul.smith at daneco.co.uk>;
>> *CC:* spce-user at lists.sipwise.com;
>>
>> Hi Paul,
>>
>> No problem. Actually have you used ngrep on spce to see the Register sent
>> by the device?
>>
>> ngrep -W byline -d eth0 REGISTER
>>
>> use putty then wait for a request and ctrl-c to exit
>>
>> copy n paste here then do the same with zoiper.
>>
>> *security note: change any external ip's from the sip message before
>> posting here in the list. ;)
>>
>> --Skyler
>>
>> On Sep 9, 2016 6:52 PM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:
>>
>> Hello Skyler,
>>
>>
>>
>> Really kind of you to be so helpful! At the moment I am just doing manual
>> config, I see the SipWise CPBX module can provision the SPA112 but perhaps
>> this is an extension for the PRO version only?
>>
>>
>>
>> I wouldn't be surprised if it's something I haven't configured properly!
>> I do see the SPA112 reports External IP as just blank. Not sure if that's
>> significant too.
>>
>>
>>
>> All the best,
>>
>>
>>
>> Paul (this is how I spend my Friday nights at 2 AM in little old England)!
>>
>>
>>
>> --
>>
>>
>> *Paul R. Smith B.Sc. (Hons.)*
>>
>> Managing Director
>>
>> Data Network Consultants Limited
>>
>>
>>
>> *T:   *01207 750 550
>>
>> *W: *www.daneco.co.uk
>>
>>
>>
>> [image: DANECO Logo]
>>
>>
>>
>> *iNorthumberland's Fixed Wireless Access Partner - Superfast Wireless
>> Network Specialists.*
>>
>>
>>
>> DANECO is a trading name of Data Network Consultants Limited.
>>
>>
>>
>> Company Reg. No: 06769055
>> Registered in England and Wales.
>>
>>
>>
>> This email and its contents are confidential and intended for the
>> addressee only. It may not be disclosed to or used by anyone else nor may
>> it be copied in any way. Data Network Consultants Limited nor the sender
>> accepts any responsibility for viruses and it is the addressee's
>> responsibility to check attachments if any. Any opinions expressed in this
>> email are those of the sender and not necessarily those of Data Network
>> Consultants Limited. If received in error please contact the sender to
>> advise then delete from your system.
>>
>>
>>
>>
>>
>>
>> -----Original message-----
>> *From:* Skyler <skchopperguy at gmail.com>
>> *Sent:* Sat 10-09-2016 01:47
>> *Subject:* Re: [Spce-user] Cisco SPA112 Configuration for SipWise
>> *To:* Paul Smith <paul.smith at daneco.co.uk>;
>> *CC:* spce-user at lists.sipwise.com;
>>
>> Hi Paul,
>>
>> Got ya. My bad as i missed the part about zoiper working. So its clearly
>> not spce config. Ok let me get home in 2 hours and i will check my nat
>> settings on the 112.
>>
>> Are you doing http/s remote provisioning or just manual right now?
>>
>> --Skyler
>>
>> On Sep 9, 2016 6:40 PM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:
>>
>> Hello Skyler,
>>
>> Thanks for that. I don't have SIP-ALG on the router and do have another
>> SPA112 unit working with a 3rd party voip system. I copied the
>> configuration to see if it would work but unfortunately not. My SipWise
>> config works with Zoiper running behind the same router which is perhaps a
>> little odd? I'm new to the soft switch World, mostly building broadband
>> networks instead. I'm keen to set up my own system rather than becoming yet
>> another Vonage reseller!
>>
>> I like things kept in house!
>>
>> Best wishes,
>>
>> Paul.
>>
>> Sent from a DANECO device.
>>
>> On 10 Sep 2016, at 1:33 am, Skyler <skchopperguy at gmail.com> wrote:
>>
>>
>> Hi Paul,
>>
>> I run mr3.8 but ive done some custom config too. i actually think the
>> problem could be spce configuration or your router, as this behavior
>> indicates a fix_nated_contact() on Register issue more than your device.
>>
>> Do you have SIP-ALG enabled on your router the ata is behind? Usually
>> thus setting tries to rewrite sip messages but in my experience it does not
>> rewrite sdp, so maybe this is the problem.
>>
>> --Skyler
>>
>> On Sep 9, 2016 5:41 PM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:
>>
>> Hello Skyler,
>>
>> Thank you for your reply. I'm running mr4.4.1 and have tried different
>> combinations of settings but without joy. Would you mind sending me a
>> generic copy of your configuration file so I can give it a try? I
>> understand if you'd rather not.
>>
>> I have updated the unit to the latest version and tried the different NAT
>> options. The unit does register and can make outbound calls but inbound
>> aren't working. SipWise is trying to route them to the private IP by the
>> look of things.
>>
>> Thank you again - any help is greatly appreciated.
>>
>> Best regards,
>>
>> Paul.
>>
>> Sent from a DANECO device.
>>
>> On 9 Sep 2016, at 11:00 pm, Skyler <skchopperguy at gmail.com> wrote:
>>
>>
>> Hi Paul,
>>
>> what version of SPCE are you using? I have an spa112 here and working for
>> me behind nat.
>>
>> --Skyler
>>
>> On Sep 9, 2016 8:58 AM, "Paul Smith" <paul.smith at daneco.co.uk> wrote:
>>
>> Hello,
>>
>>
>>
>> Further to my last e-mail, I have had Cisco support on the phone and
>> using remote desktop for over an hour and they could not solve the problem!
>>
>>
>>
>> I notice that the SPA112 registers as follows:
>> Cisco/SPA112-1.4.1(002) sip:xxxxxxxxxxxx at 192.168.1.60:5060
>>
>>
>>
>>
>>
>> Is the fact that it is registering with its LAN IP significant as I
>> believe it to be? When I assign the same account to a Zoiper softphone, it
>> registers with the correct external IP address. I am going to experiment
>> with the SPA112 sitting directly on a public IP address and see if it
>> registers with SipWise correctly.
>>
>>
>>
>> Raúl - Gemma will be in touch with those login details soon. I am hoping
>> to at least get a test account running so that you can see our
>> configuration and determine how much support we need!
>>
>>
>>
>> Very best of wishes,
>>
>>
>>
>> Paul.
>>
>>
>>
>> --
>>
>>
>> *Paul R. Smith B.Sc. (Hons.)*
>>
>> Managing Director
>>
>> Data Network Consultants Limited
>>
>>
>>
>> *T:   *01207 750 550
>>
>> *W: *www.daneco.co.uk
>>
>>
>>
>> [image: DANECO Logo]
>>
>>
>>
>> *iNorthumberland's Fixed Wireless Access Partner - Superfast Wireless
>> Network Specialists.*
>>
>>
>>
>> DANECO is a trading name of Data Network Consultants Limited.
>>
>>
>>
>> Company Reg. No: 06769055
>> Registered in England and Wales.
>>
>>
>>
>> This email and its contents are confidential and intended for the
>> addressee only. It may not be disclosed to or used by anyone else nor may
>> it be copied in any way. Data Network Consultants Limited nor the sender
>> accepts any responsibility for viruses and it is the addressee's
>> responsibility to check attachments if any. Any opinions expressed in this
>> email are those of the sender and not necessarily those of Data Network
>> Consultants Limited. If received in error please contact the sender to
>> advise then delete from your system.
>>
>>
>>
>>
>>
>>
>> -----Original message-----
>> *From:* Paul Smith <paul.smith at daneco.co.uk>
>> *Sent:* Thu 08-09-2016 19:19
>> *Subject:* [Spce-user] Cisco SPA112 Configuration for SipWise
>> *To:* Spce-user at lists.sipwise.com;
>>
>> Dear All,
>>
>>
>>
>> My apologies if this subject has already been covered, but I wondered if
>> someone could point me in the right direction for a working configuration
>> on the Cisco SPA112?
>>
>>
>>
>> I can place outbound calls fine, but inbound are a no-go. I suspect this
>> is because the SPA112 is registering with its internal IP address rather
>> than that of the WAN connection. I have enabled NAT mapping and keep alive
>> but this hasn't made a difference.
>>
>>
>>
>> Any help would be greatly appreciated.
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Paul.
>>
>>
>>
>> --
>>
>>
>> *Paul R. Smith B.Sc. (Hons.)*
>>
>> Managing Director
>>
>> Data Network Consultants Limited
>>
>>
>>
>> *T:   *01207 750 550
>>
>> *W: *www.daneco.co.uk
>>
>>
>>
>> [image: DANECO Logo]
>>
>>
>>
>> *iNorthumberland's Fixed Wireless Access Partner - Superfast Wireless
>> Network Specialists.*
>>
>>
>>
>> DANECO is a trading name of Data Network Consultants Limited.
>>
>>
>>
>> Company Reg. No: 06769055
>> Registered in England and Wales.
>>
>>
>>
>> This email and its contents are confidential and intended for the
>> addressee only. It may not be disclosed to or used by anyone else nor may
>> it be copied in any way. Data Network Consultants Limited nor the sender
>> accepts any responsibility for viruses and it is the addressee's
>> responsibility to check attachments if any. Any opinions expressed in this
>> email are those of the sender and not necessarily those of Data Network
>> Consultants Limited. If received in error please contact the sender to
>> advise then delete from your system.
>>
>>
>>
>>   _______________________________________________
>>  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
>>
>>
>>
>> _______________________________________________
>>  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/20160909/185c2619/attachment.html>

More information about the Spce-user mailing list