[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
T48G units with OpenVPN through pfSense
Author Message
cmariotti Offline
Junior Member
**

Posts: 9
Joined: Jun 2013
Reputation: 0
Post: #1
T48G units with OpenVPN through pfSense
I am trying to debug a problem with a phone that is being setup with OpenVPN.

The tunnel is up, I can ping the phone... If I call that extension, I can receive the call but the phone never registers... (No Service, flashing extension)

if I try to dial an extension from that phone, or dial feature (*97) or phone number... I get "unknown uri scheme". It also appears that there is no SIP communications in this case, nothing captured in the packets.

Any ideas?
01-10-2016 01:30 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Karl_Yealink Offline
Super Moderator
******

Posts: 673
Joined: Apr 2015
Reputation: 5
Post: #2
RE: T48G units with OpenVPN through pfSense
Do you register an account in the phone?
01-11-2016 06:03 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
cmariotti Offline
Junior Member
**

Posts: 9
Joined: Jun 2013
Reputation: 0
Post: #3
RE: T48G units with OpenVPN through pfSense
(01-11-2016 06:03 PM)Yealink_Karl Wrote:  Do you register an account in the phone?

I have tried, but it is not registering...
01-12-2016 12:43 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
cmariotti Offline
Junior Member
**

Posts: 9
Joined: Jun 2013
Reputation: 0
Post: #4
RE: T48G units with OpenVPN through pfSense
Here are logs from the asterisk box logging extension 222...

Reliably Transmitting (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK4cc58e92;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as39f66fd7
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #1 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK4cc58e92;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as39f66fd7
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #2 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK4cc58e92;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as39f66fd7
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #3 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK4cc58e92;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as39f66fd7
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #4 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK4cc58e92;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as39f66fd7
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:20 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Really destroying SIP dialog '5c17f60204dde9e57ec9699624d1dc13@192.168.10.71:5060' Method: OPTIONS
[2016-01-11 13:14:33] NOTICE[3178]: chan_sip.c:12578 sip_reregister: -- Re-registration for 194583_cruc@newyork4.voip.ms
[2016-01-11 13:14:33] NOTICE[3178]: chan_sip.c:20043 handle_response_register: Outbound Registration: Expiry for newyork4.voip.ms is 120 sec (Scheduling reregistration in 105 s)
Reliably Transmitting (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK798a35a0;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as32ba7931
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 45477ae05feee6631077870868f4065f@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #1 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK798a35a0;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as32ba7931
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 45477ae05feee6631077870868f4065f@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #2 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK798a35a0;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as32ba7931
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 45477ae05feee6631077870868f4065f@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #3 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK798a35a0;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as32ba7931
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 45477ae05feee6631077870868f4065f@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Retransmitting #4 (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK798a35a0;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as32ba7931
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 45477ae05feee6631077870868f4065f@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---
Really destroying SIP dialog '45477ae05feee6631077870868f4065f@192.168.10.71:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.6:5060 --->
REGISTER sip:192.168.10.71:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK4272262690
From: "222" <sip:222@192.168.10.71:5060>;tag=3905153404
To: "222" <sip:222@192.168.10.71:5060>
Call-ID: 0_944913946@192.168.15.6
CSeq: 1 REGISTER
Contact: <sip:222@192.168.15.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T48G 35.80.0.70
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (13 headers 0 lines) ---
Sending to 192.168.15.6:5060 (NAT)

<--- Transmitting (NAT) to 192.168.15.6:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK4272262690;received=192.168.15.6;rport=5060
From: "222" <sip:222@192.168.10.71:5060>;tag=3905153404
To: "222" <sip:222@192.168.10.71:5060>;tag=as3a6ef5e7
Call-ID: 0_944913946@192.168.15.6
CSeq: 1 REGISTER
Server: FPBX-2.11.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="39391f21"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_944913946@192.168.15.6' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.15.6:5060 --->
REGISTER sip:192.168.10.71:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK2755642380
From: "222" <sip:222@192.168.10.71:5060>;tag=4235170210
To: "222" <sip:222@192.168.10.71:5060>
Call-ID: 0_3731632758@192.168.15.6
CSeq: 1 REGISTER
Contact: <sip:222@192.168.15.6:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T48G 35.80.0.70
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (13 headers 0 lines) ---
Sending to 192.168.15.6:5060 (NAT)

<--- Transmitting (NAT) to 192.168.15.6:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK2755642380;received=192.168.15.6;rport=5060
From: "222" <sip:222@192.168.10.71:5060>;tag=4235170210
To: "222" <sip:222@192.168.10.71:5060>;tag=as7d82018d
Call-ID: 0_3731632758@192.168.15.6
CSeq: 1 REGISTER
Server: FPBX-2.11.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="55a9d761"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_3731632758@192.168.15.6' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.15.6:5060 --->
REGISTER sip:192.168.10.71:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK3305336958
From: "222" <sip:222@192.168.10.71:5060>;tag=4235170210
To: "222" <sip:222@192.168.10.71:5060>
Call-ID: 0_3731632758@192.168.15.6
CSeq: 2 REGISTER
Contact: <sip:222@192.168.15.6:5060>
Authorization: Digest username="222", realm="asterisk", nonce="55a9d761", uri="sip:192.168.10.71:5060", response="66d7a61f98efe9b26345bcbe307d0410", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T48G 35.80.0.70
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.15.6:5060 (NAT)
Reliably Transmitting (NAT) to 192.168.15.6:5060:
OPTIONS sip:222@192.168.15.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK7a1edc58;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as1d9cc1fa
To: <sip:222@192.168.15.6:5060>
Contact: <sip:Unknown@192.168.10.71:5060>
Call-ID: 4b5f9373485af89d306acdb549b8d6bb@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(1.8.5.0)
Date: Mon, 11 Jan 2016 18:14:41 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- Transmitting (NAT) to 192.168.15.6:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.6:5060;branch=z9hG4bK3305336958;received=192.168.15.6;rport=5060
From: "222" <sip:222@192.168.10.71:5060>;tag=4235170210
To: "222" <sip:222@192.168.10.71:5060>;tag=as7d82018d
Call-ID: 0_3731632758@192.168.15.6
CSeq: 2 REGISTER
Server: FPBX-2.11.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 3600
Contact: <sip:222@192.168.15.6:5060>;expires=3600
Date: Mon, 11 Jan 2016 18:14:41 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_3731632758@192.168.15.6' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.15.6:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.71:5060;branch=z9hG4bK7a1edc58;rport=5060
From: "Unknown" <sip:Unknown@192.168.10.71>;tag=as1d9cc1fa
To: <sip:222@192.168.15.6:5060>;tag=1707942526
Call-ID: 4b5f9373485af89d306acdb549b8d6bb@192.168.10.71:5060
CSeq: 102 OPTIONS
User-Agent: Yealink SIP-T48G 35.80.0.70
Content-Length: 0

<------------->
--- (8 headers 0 lines) ---
[2016-01-11 13:14:41] NOTICE[3178]: chan_sip.c:20087 handle_response_peerpoke: Peer '222' is now Reachable. (36ms / 2000ms)
Really destroying SIP dialog '4b5f9373485af89d306acdb549b8d6bb@192.168.10.71:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.6:5060 --->


<------------->
Really destroying SIP dialog '0_944913946@192.168.15.6' Method: REGISTER
Really destroying SIP dialog '0_3731632758@192.168.15.6' Method: REGISTER
CIPBX01*CLI>
01-12-2016 02:08 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
cmariotti Offline
Junior Member
**

Posts: 9
Joined: Jun 2013
Reputation: 0
Post: #5
RE: T48G units with OpenVPN through pfSense
I just re-did this scenario with a completely different setup with the same results...

"V" is there, can ping it, can call that extension and answer without issue, but still can't make any calls or features (*97)... same as above.
01-12-2016 02:29 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Karl_Yealink Offline
Super Moderator
******

Posts: 673
Joined: Apr 2015
Reputation: 5
Post: #6
RE: T48G units with OpenVPN through pfSense
There are something want to confirm again.
1. Can you register the account succeed? If you haven't a reistered account, how can the phone receive the incoming call?
2. From your description, can I understand that you can take incoming call, but you can't take outgoing call?
3. What firmware of the phone?
4. Would you please help us to get the PCAP and syslog and config files, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319 
5. It's better you can alos give me the log info from asterisk box.

You can email to me(karl@yealink.com), if you don't want the files public.

BTW, I find the other post: http://forum.yealink.com/forum/showthrea...6#pid26416
Do they are the same issue?
(This post was last modified: 01-12-2016 04:18 PM by Karl_Yealink.)
01-12-2016 04:09 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
cmariotti Offline
Junior Member
**

Posts: 9
Joined: Jun 2013
Reputation: 0
Post: #7
RE: T48G units with OpenVPN through pfSense
(01-12-2016 04:09 PM)Yealink_Karl Wrote:  There are something want to confirm again.
1. Can you register the account succeed? If you haven't a reistered account, how can the phone receive the incoming call?
2. From your description, can I understand that you can take incoming call, but you can't take outgoing call?
3. What firmware of the phone?
4. Would you please help us to get the PCAP and syslog and config files, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319 
5. It's better you can alos give me the log info from asterisk box.

You can email to me(karl@yealink.com), if you don't want the files public.

BTW, I find the other post: http://forum.yealink.com/forum/showthrea...6#pid26416
Do they are the same issue?

Yes, they seem to be related.
I will compile and send the information now.

(01-12-2016 04:09 PM)Yealink_Karl Wrote:  There are something want to confirm again.
1. Can you register the account succeed? If you haven't a reistered account, how can the phone receive the incoming call?
2. From your description, can I understand that you can take incoming call, but you can't take outgoing call?
3. What firmware of the phone?
4. Would you please help us to get the PCAP and syslog and config files, we can check something from them.
You can get more info from the link: http://forum.yealink.com/forum/showthread.php?tid=1319 
5. It's better you can alos give me the log info from asterisk box.

You can email to me(karl@yealink.com), if you don't want the files public.

BTW, I find the other post: http://forum.yealink.com/forum/showthrea...6#pid26416
Do they are the same issue?

They are running the latest firmware as well... I could not get the VPN operational without it.
(This post was last modified: 01-12-2016 10:01 PM by cmariotti.)
01-12-2016 10:00 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  T41P/T48G/T58V IPv6 SIP Issues ReubenFarrelly 22 40,304 08-01-2021 06:14 PM
Last Post: Phil2021
Question T48G + WH66 Futureweb 1 1,704 06-09-2021 09:22 PM
Last Post: Futureweb
  T41P and OpenVPN coltarushalo 0 1,403 05-26-2021 02:58 AM
Last Post: coltarushalo
  T46G/T48G no Ringtone because of 183 insted of ringing eurix 2 2,589 04-09-2021 05:16 PM
Last Post: eurix
  Packet Capture - T4x w/OpenVPN coltarushalo 0 1,309 03-13-2021 01:15 AM
Last Post: coltarushalo
  OpenVPN issue with SIP/UDP fredoch 0 1,787 11-10-2020 03:47 PM
Last Post: fredoch
  WF50 wifi adapter on T48G? freak 2 5,662 10-31-2020 05:41 AM
Last Post: SCPCJNR
  T48G Onscreen keyboard languages eliah 7 11,894 10-30-2020 06:51 PM
Last Post: complex1
  OpenVPN Version List coltarushalo 0 1,626 08-03-2020 08:35 PM
Last Post: coltarushalo
  t48G SFB not working at all now j.pakula 0 1,790 06-22-2020 02:36 PM
Last Post: j.pakula

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication