Odd issue after upgrade(just a guess)

Status
Not open for further replies.

rkbsimpsipper

New Member
Jan 3, 2022
20
1
3
40
The pbx server seems to read my sip expire timer at 60 seconds more than what is set on the phones. Which makes them drop out when the expire timer lapses, at least to my un trained eye. Has anyone had this issue?

Any help is appreciated

Thanks

KB
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,032
554
113
Use sngrep and find out what the server sends in the 200OK to the registration.

The pbx may well be overriding what the phone set bit the phones should be respecting that.
 

rkbsimpsipper

New Member
Jan 3, 2022
20
1
3
40
Thanks for the reply.

It shows the correct info
```
192.168.4.2:1213 192.168.3.53:5060 │Via: SIP/2.0/TCP 192.168.4.2:1213;branch=z9hG4bK3008350805629544457;rport=1213
──────────┬───────── ──────────┬─────────│From: Shelburne 1102 <sip:1102@e1p.OMITTED.org>;tag=2794011277
08:53:52.337148 │ REGISTER │ │To: OMITTED 1102 <sip:1102@e1p.OMITTED.org>;tag=NcD569BBrt99K
+0.000730 │ ──────────────────────────> │ │Call-ID: 618244026232590-396525605753073@10.10.150.74
08:53:52.337878 │ 401 Unauthorized │ │CSeq: 16 REGISTER
+0.165171 │ <────────────────────────── │ │Contact: <sip:1102@192.168.4.2:1213;transport=tcp>;expires=120
08:53:52.503049 │ REGISTER │ │Date: Mon, 04 Dec 2023 14:53:53 GMT
+0.004196 │ ──────────────────────────> │ │User-Agent: FreeSWITCH
08:53:52.507245 │ 200 OK │ │Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY,
-30.810448 │ <────────────────────────── │ │UBLISH, SUBSCRIBE
08:54:21.876353 │ REGISTER │ │Supported: path, replaces
-31.015457 │ ──────────────────────────> │ │Content-Length: 0
```

But shows this in the WEBUI

1701702054754.png
 

rkbsimpsipper

New Member
Jan 3, 2022
20
1
3
40
So I updated my udm-pro where this is hosted... For whatever reason this was the issue. In the Security Module(I am running the RC version for site magic)Voip was not set in the detection sensitivity list, but the vlan was in the monitor list. Removing it fixed/Solved the problem. This has never been as issue before. Either way, sorry for bringing my dirty laundry here lol

KB
 
  • Like
Reactions: DigitalDaz
Status
Not open for further replies.