J100 remote phone acquiring service

[teletechman]

I have a J169 that I am trying to connect to a site remotely. The ports are forwarded per their IT provider. I know this is not the best way to do this, but the IT provider is locking down all remote phones via the end users IP address. We get the phone to connect when it is a STD SIP phone but when trying to connect as a feature SIP phone it goes to acquiring service and keeps doing the Avaya login sound over and over. When I look at the trace it shows the phone registering but then says TCP broken and starts a reregister of the phone. xxx.xxx.xxx.xxx is my public address of the remote location and it is correct, 10.20.25.84 is the private address of the remote phone and 192.168.11.50 is the IP Office.
Can't seem to find why these will not connect.
Mike

 

[derfloh]

Probably the HTTPS connection is not fully functional.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[teletechman]

I am not using HTTPS I have loaded all the settings via a HTTP server local to the phone it does not access the HTTP or HTTPS server during log in.
Mike

 

[derfloh]

But it needs the connection to the IPO MTCTI service through port 443.

It’s essential to load contacts, call log and it’s used to do all the call control.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[teletechman]

this did not change anything, we opened the port and it still keeps cycling through logging in and show acquiring service. The phone is then quarantined but keeps cycling on acquiring service.
Mike

 

[derfloh]

What das Sysmon say?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[teletechman]

do you mean System Monitor? I included that in the original post.
Mike

 

[derfloh]

Sorry, overlooked it…

I don’t see any HTTP traffic. Probably because the filter is not set.

Nevertheless… You use TCP connection for the phone instead of TLS. Apart from the strictly not recommended direct connection (without SBC) from public Internet to the IPO (!!!) using an unencrypted connection is a no go!

Additionally since you connect without encryption you will probably have no valid certificate. And while the service connection of the phone uses HTTPS valid certificates are a must.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN