D100 and D160 - Trying to Login resets base station

[Pepp77]

I am currently testing the D100 and D160 DECT on my test kit. System is on 9.0.6 and has all the relevant licencing.

I have configured the base station in Manager as well as a user and I can see the base station registered in SSA and I am able to register a handset to the base station. If I dial an extension from the handset it rings the handset fine and we get two way speech.

I have one major issue though whenever I choose the login option on the phone and enter the extension number and password associated to the user the base station resets, the phone doesn't login and the error is 403 Forbidden.

This is what monitor shows

12:18:21 1644841mS PRN: D100BaseStation::ResetBaseStationInfo()
12:18:23 1646099mS SIP Rx: UDP 192.168.55.212:5060 -> 192.168.55.84:5060
REGISTER sip:192.168.55.84:5060 SIP/2.0
From: <sip:6000@192.168.55.84>;tag=e9b270-d437a8c0-13c4-6006-299-0-299
To: <sip:6000@192.168.55.84>
Call-ID: ec2516-d437a8c0-13c4-6006-299-0-299
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.55.212:5060;rport;branch=z9hG4bK-299-a2978-0-e85408
Max-Forwards: 70
Supported: replaces,100rel,timer
User-Agent: Avaya D100 (D100_0.8.6_0.9.6 00:E0:11:0B:13:92)
Expires: 180
Contact: <sip:6000@192.168.55.212:5060>
Content-Length: 0

12:18:23 1646101mS SIP Reg/Opt Rx: phone
REGISTER sip:192.168.55.84:5060 SIP/2.0
From: <sip:6000@192.168.55.84>;tag=e9b270-d437a8c0-13c4-6006-299-0-299
To: <sip:6000@192.168.55.84>
Call-ID: ec2516-d437a8c0-13c4-6006-299-0-299
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.55.212:5060;rport;branch=z9hG4bK-299-a2978-0-e85408
Max-Forwards: 70
Supported: replaces,100rel,timer
User-Agent: Avaya D100 (D100_0.8.6_0.9.6 00:E0:11:0B:13:92)
Expires: 180
Contact: <sip:6000@192.168.55.212:5060>
Content-Length: 0

12:18:23 1646101mS Sip: SIPDialog f4a8b0cc created, dialogs 1
12:18:23 1646102mS Sip: SIP REG: D100 registration (mac=00:E0:11:0B:13:92, extn=6000)
12:18:23 1646102mS Sip: SIP REG: invalid D100 registration (mac=00:E0:11:0B:13:92, extn=6000)
12:18:23 1646103mS SIP Reg/Opt Tx: phone
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.55.212:5060;rport;branch=z9hG4bK-299-a2978-0-e85408
From: <sip:6000@192.168.55.84>;tag=e9b270-d437a8c0-13c4-6006-299-0-299
Call-ID: ec2516-d437a8c0-13c4-6006-299-0-299
CSeq: 1 REGISTER
User-Agent: IP Office 9.0.4.0 build 965
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.4.0 build 965
Reason: Q.850;cause=21;text="Call rejected"
To: <sip:6000@192.168.55.84>;tag=39e6ea194873a470
Content-Length: 0

12:18:23 1646104mS SIP Tx: UDP 192.168.55.84:5060 -> 192.168.55.212:5060
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.55.212:5060;rport;branch=z9hG4bK-299-a2978-0-e85408
From: <sip:6000@192.168.55.84>;tag=e9b270-d437a8c0-13c4-6006-299-0-299
Call-ID: ec2516-d437a8c0-13c4-6006-299-0-299
CSeq: 1 REGISTER
User-Agent: IP Office 9.0.4.0 build 965
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.4.0 build 965
Reason: Q.850;cause=21;text="Call rejected"
To: <sip:6000@192.168.55.84>;tag=39e6ea194873a470
Content-Length: 0

I cannot work out what the issue is, I have tried it with two base stations, two handsets and have deleted and recreated the SIP programming numerous times. The only thing I haven't tried is it on a different phone system.

Any ideas?

| ACSS SME |

 

[Pepp77]

Okay odd one. I removed the programming from my test system and added the programming to my lab system (both are on 9.0.4). Nothing else changed and now the handsets will login without any issue.

So same settings on base station (except Configuration server IP address) and same settings on the different phone systems, one works fine the other not!

| ACSS SME |

 

[azrael2000]

Hi there.

I wonder if you are having the same... or if not the same, then similar problem to what I was having.

I had a dect d100 set I needed to put on my 9.1.1 system, and it wouldn't register to the ip office. After I put it on a 9.0 system it pulled the files it needed and then would register to the 9.1.

After you have put it on your test system, did you try it on the "real" system.

Regards

 

[Pepp77]

And the plot thickens

Azrael - I havent tried yet no, I have been having other issues.

The sales team have sold these devices to fit the following scenario

Head office - BT installed IPO on 9.0.4.
2 x Satellite offices connected to the head office via P2P VPNs on Draytek routers.

The D100 are to be installed at the satellite offices, one base station and two phones per office.

As a result I have setup my scenario as follows to try and as closely replicate as I can in house.

IPO on 192.168.55.46 on LAN1
This then connects to a basic router set to 192.168.55.222 on its WAN with a LAN subnet of 192.168.57.x.
The base station I set to 192.168.57.212 with a gateway of 192.168.57.1 (Router LAN IP Address).

The base station registers to the IPO fine and I can make a call from the handset registered to the base station as no user, the problem occurs when I try to actually log a user into that handset I just get the following


********** Warning: Logging to Screen Started **********
00:43:44 60302139mS Sip: SIP REG: LAN(192.168.55.46) has no public address provisioned for remote worker
00:43:44 60302200mS Sip: SIP REG: LAN(192.168.55.46) has no public address provisioned for remote worker
00:43:44 60302845mS RES: Wed 3/6/2015 00:43:44 FreeMem=54360800 53934856(16) CachedMem=425944 CMMsg=1(1) Buff=5200 1364 1000 7442 5 Links=8279 BTree=14495 CPU=12.48% CPUStats=3/7/6100/20360/26541/0/0 MCR=10752 MCW=0
00:43:44 60302845mS RES2: IP 500 V2 9.0.4.0 build 965 Tasks=50 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=58 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=1 TCP=20(TLS=4) TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
00:43:44 60302845mS RES4: XML MemObjs=61 PoolMem=2097152(1) FreeMem=2081872(1)
00:43:48 60307845mS RES: Wed 3/6/2015 00:43:49 FreeMem=54380304 53934856(16) CachedMem=445448 CMMsg=1(1) Buff=5200 1364 1000 7415 5 Links=8303 BTree=14495 CPU=07.56% CPUStats=10/21/6100/21883/26541/0/0 MCR=0 MCW=0
00:43:48 60307845mS RES2: IP 500 V2 9.0.4.0 build 965 Tasks=50 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=61 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=1 TCP=19(TLS=4) TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
00:43:48 60307845mS RES4: XML MemObjs=61 PoolMem=2097152(1) FreeMem=2081872(1)
00:43:49 60308853mS SIP Rx: UDP 192.168.55.222:55014 -> 192.168.55.46:5060
REGISTER sip:192.168.55.46:5060 SIP/2.0
From: <sip:555@192.168.55.46>;tag=e99220-d439a8c0-13c4-6006-d603-0-d603
To: <sip:555@192.168.55.46>
Call-ID: ec1fb6-d439a8c0-13c4-6006-d603-0-d603
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.57.212:5060;rport;branch=z9hG4bK-d603-343fc08-0-e83678
Max-Forwards: 70
Supported: replaces,100rel,timer
User-Agent: Avaya D100 (D100_0.8.6_0.9.6 00:E0:11:0B:17:ED)
Expires: 180
Contact: <sip:555@192.168.57.212:5060>
Content-Length: 0

00:43:49 60308855mS SIP Reg/Opt Rx: phone
REGISTER sip:192.168.55.46:5060 SIP/2.0
From: <sip:555@192.168.55.46>;tag=e99220-d439a8c0-13c4-6006-d603-0-d603
To: <sip:555@192.168.55.46>
Call-ID: ec1fb6-d439a8c0-13c4-6006-d603-0-d603
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.57.212:5060;rport;branch=z9hG4bK-d603-343fc08-0-e83678
Max-Forwards: 70
Supported: replaces,100rel,timer
User-Agent: Avaya D100 (D100_0.8.6_0.9.6 00:E0:11:0B:17:ED)
Expires: 180
Contact: <sip:555@192.168.57.212:5060>
Content-Length: 0

00:43:49 60308855mS Sip: SIPDialog f4e20f60 created, dialogs 1
00:43:49 60308856mS Sip: SIP REG: LAN(192.168.55.46) has no public address provisioned for remote worker
00:43:49 60308856mS Sip: SIP REG: extn 555 address restricted
00:43:49 60308858mS SIP Reg/Opt Tx: phone
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.57.212:5060;rport;branch=z9hG4bK-d603-343fc08-0-e83678
From: <sip:555@192.168.55.46>;tag=e99220-d439a8c0-13c4-6006-d603-0-d603
Call-ID: ec1fb6-d439a8c0-13c4-6006-d603-0-d603
CSeq: 1 REGISTER
User-Agent: IP Office 9.0.4.0 build 965
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.4.0 build 965
Reason: Q.850;cause=21;text="Call rejected"
To: <sip:555@192.168.55.46>;tag=4870ec6643b7fc39
Content-Length: 0

00:43:49 60308858mS SIP Tx: UDP 192.168.55.46:5060 -> 192.168.55.222:55014
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.57.212:5060;rport;branch=z9hG4bK-d603-343fc08-0-e83678
From: <sip:555@192.168.55.46>;tag=e99220-d439a8c0-13c4-6006-d603-0-d603
Call-ID: ec1fb6-d439a8c0-13c4-6006-d603-0-d603
CSeq: 1 REGISTER
User-Agent: IP Office 9.0.4.0 build 965
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Supported: timer
Server: IP Office 9.0.4.0 build 965
Reason: Q.850;cause=21;text="Call rejected"
To: <sip:555@192.168.55.46>;tag=4870ec6643b7fc39
Content-Length: 0

00:43:49 60308858mS Sip: SIPDialog f4e20f60 deleted, dialogs 0

********** Warning: Logging to Screen Stopped **********


| ACSS SME |