Basically, have traced the issue back to the Line side failure.
I'm admittedly not a phone guy, security. Have searched the internet and found nothing that would help me fix this issue.
Wondering if there is anything I am blatantly missing
Also, I noticed that the connect method, in this case, is TCP instead of UDP. I'm assuming that this is because the connect method is listed as a cellular network, which chooses TCP over UDP for reliability
<sipaloalto@10.100.10.117:5060;transport=TCP>;expires=480;boottime=1559317364;sequenceid=15;deviceid=(removed);service=data;linktype=cell-data>
I also noticed that on the working one the port is 5070 not 5060 is this because of the use of TCP or is this some sort of issue?
SIP/2.0 503 Policy check failure
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - From: <sipaloalto@172.31.25.5:5060;transport=TCP>;tag=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - To: <sipaloalto@172.31.25.5:5060>;tag=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Call-ID: (reomved)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - CSeq: 1 REGISTER
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Via: SIP/2.0/TCP 10.100.10.117:5060;alias;branch=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Reason: SIP;cause=503;text="Line side is not registered"
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Register-Counter: 24
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - User-Agent: ShoreTelMR/9.5.1809.105
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Content-Length: 0
Please let me know if you need more details or having a working GP and Mitel setup that I could follow.
Willing to answer any PA Firewall question in return.
I'm admittedly not a phone guy, security. Have searched the internet and found nothing that would help me fix this issue.
Wondering if there is anything I am blatantly missing
Also, I noticed that the connect method, in this case, is TCP instead of UDP. I'm assuming that this is because the connect method is listed as a cellular network, which chooses TCP over UDP for reliability
<sipaloalto@10.100.10.117:5060;transport=TCP>;expires=480;boottime=1559317364;sequenceid=15;deviceid=(removed);service=data;linktype=cell-data>
I also noticed that on the working one the port is 5070 not 5060 is this because of the use of TCP or is this some sort of issue?
SIP/2.0 503 Policy check failure
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - From: <sipaloalto@172.31.25.5:5060;transport=TCP>;tag=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - To: <sipaloalto@172.31.25.5:5060>;tag=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Call-ID: (reomved)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - CSeq: 1 REGISTER
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Via: SIP/2.0/TCP 10.100.10.117:5060;alias;branch=(removed)
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Reason: SIP;cause=503;text="Line side is not registered"
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Register-Counter: 24
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - User-Agent: ShoreTelMR/9.5.1809.105
05/31/2019 10:43:27:886 I/CallCt (0x16e39b000) RvSip: INFO - TRANSPORT - Content-Length: 0
Please let me know if you need more details or having a working GP and Mitel setup that I could follow.
Willing to answer any PA Firewall question in return.