Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3


67 posts

Master Geek
+1 received by user: 7


  Reply # 1512573 13-Mar-2016 21:10
Send private message

toejam316:
Clima:
BarTender: So just confirming the issue. It's not that you don't get caller id... it's that it doesn't indicate the date and time.

My dect phone has the time set in the handset. So any caller id has the time of the handset.

 

 

Not what I would expect. Previously the date and time definitely came from transmission as shown when Orcon didn't update with daylight saving.

 

 

As far as I understand Caller ID as a standard, it's only number or directory name + number transmitted, everything else is the job of your CPE (in this case, your cordless).

 

 

I am not sure what the specification is on voip - which is part of the reason for this thread. Under POTS the information was transmitted between the first and second ring cadence and the "message" included the caller with date and time as added by the final carrier.

5243 posts

Uber Geek
+1 received by user: 2259

Trusted
Lifetime subscriber

  Reply # 1512575 13-Mar-2016 21:13
Send private message

Check you CPE (router) is correctly picking up the correct  time from an internet time server.

 

 





Chorus has spent $1.4 billion on making their xDSL broadband network faster. If your still stuck on ADSL or VDSL, why not spend from $150 on a master filter install to make sure you are getting the most out of your connection?
I install - Naked DSL, DSL Master Splitters, VoIP, data cabling and general computer support for home and small business.
Rural Broadband RBI installer for Ultimate Broadband and Full Flavour

 

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com




67 posts

Master Geek
+1 received by user: 7


  Reply # 1512583 13-Mar-2016 21:19
Send private message

coffeebaron:

Check you CPE (router) is correctly picking up the correct  time from an internet time server.

 

 

 

 

Yes router is getting correct time from internet. My problem is no display of date and time but the number is shown.

 


1508 posts

Uber Geek
+1 received by user: 572


  Reply # 1512603 13-Mar-2016 21:56
Send private message

Clima:
toejam316:
Clima:
BarTender: So just confirming the issue. It's not that you don't get caller id... it's that it doesn't indicate the date and time.

My dect phone has the time set in the handset. So any caller id has the time of the handset.
Not what I would expect. Previously the date and time definitely came from transmission as shown when Orcon didn't update with daylight saving.
As far as I understand Caller ID as a standard, it's only number or directory name + number transmitted, everything else is the job of your CPE (in this case, your cordless).
I am not sure what the specification is on voip - which is part of the reason for this thread. Under POTS the information was transmitted between the first and second ring cadence and the "message" included the caller with date and time as added by the final carrier.

 

 

 

There's no special "caller ID for VoIP", your router simply takes the place of the telephone exchange, and generates the same codes as used on POTS and send it to your phone.




67 posts

Master Geek
+1 received by user: 7


  Reply # 1512623 13-Mar-2016 22:22
Send private message

DarkShadow:

Clima:
toejam316:
Clima:
BarTender: So just confirming the issue. It's not that you don't get caller id... it's that it doesn't indicate the date and time.

My dect phone has the time set in the handset. So any caller id has the time of the handset.
Not what I would expect. Previously the date and time definitely came from transmission as shown when Orcon didn't update with daylight saving.
As far as I understand Caller ID as a standard, it's only number or directory name + number transmitted, everything else is the job of your CPE (in this case, your cordless).
I am not sure what the specification is on voip - which is part of the reason for this thread. Under POTS the information was transmitted between the first and second ring cadence and the "message" included the caller with date and time as added by the final carrier.

 

 

 

There's no special "caller ID for VoIP", your router simply takes the place of the telephone exchange, and generates the same codes as used on POTS and send it to your phone.

 

 

Thank you.

 

 

Does the router use its date and time or is it received as part of the call setup phase?

 

 

Whichever I guess in this case the router is either incompatible with the incoming data or is not doing its part and providing the information.

2355 posts

Uber Geek
+1 received by user: 374

Trusted

  Reply # 1512626 13-Mar-2016 22:45
Send private message

If people want to read about it.. its all explained in TNA 102, Section 10 onwards

 

Onhook data transmission . The date/time and callerid is sent via between the 1st and 2nd rings (via the POTS side)

 

 

 

 

 

 

 

 




67 posts

Master Geek
+1 received by user: 7


  Reply # 1512627 13-Mar-2016 22:53
Send private message

LennonNZ:

If people want to read about it.. its all explained in TNA 102, Section 10 onwards

 

Onhook data transmission . The date/time and callerid is sent via between the 1st and 2nd rings (via the POTS side)

 

 

 

 

 

 

 

 

 

 

Yes Thanks.

 

 

In the VOIP case who is responsible for the date and time information - the router or the data via the ONT

796 posts

Ultimate Geek
+1 received by user: 262

Trusted

  Reply # 1512633 13-Mar-2016 23:12
Send private message

Using VoIP from 2degrees. Delivered via a Fritzbox. The cordless phones learn the date/time on their own. Haven't ever set it up. Caller ID works as expected, shows the number of the caller. Phones don't display a date/time when a call came in, and never have.

 

Previously when using VFX have seen the caller ID show the name of the account holder (from a Slingshot line, possibly UCLL), however haven't seen this since the VoIP moved to 2degrees.


1594 posts

Uber Geek
+1 received by user: 408


  Reply # 1512636 13-Mar-2016 23:18
Send private message

I had this problem when associating the phone handset with the orcon router itself instead of its original base station via the phone port.



67 posts

Master Geek
+1 received by user: 7


  Reply # 1512638 13-Mar-2016 23:25
Send private message

MadEngineer: I had this problem when associating the phone handset with the orcon router itself instead of its original base station via the phone port.

 

 

Thanks. I have the Uniden base connected to the NF4V phone port. The DECT3035 handsets connect via the Uniden base.



67 posts

Master Geek
+1 received by user: 7


  Reply # 1512650 13-Mar-2016 23:30
Send private message

Lorenceo:

Using VoIP from 2degrees. Delivered via a Fritzbox. The cordless phones learn the date/time on their own. Haven't ever set it up. Caller ID works as expected, shows the number of the caller. Phones don't display a date/time when a call came in, and never have.

 

Previously when using VFX have seen the caller ID show the name of the account holder (from a Slingshot line, possibly UCLL), however haven't seen this since the VoIP moved to 2degrees.

 

 

(thought I had replied - must have lost it)

 

 

Interesting !! how can the phones learn T&D ? Most phones with caller-ID get their T&D from the caller-ID 'message'

 

 

So 2D and Fritzbox don't give full Caller-ID information either.



67 posts

Master Geek
+1 received by user: 7


  Reply # 1512656 14-Mar-2016 00:11
Send private message

MadEngineer: I had this problem when associating the phone handset with the orcon router itself instead of its original base station via the phone port.

 

 

Are you with Orcon on UFB using a NF4V and getting full caller information ?

26921 posts

Uber Geek
+1 received by user: 6356

Moderator
Trusted
Biddle Corp
Lifetime subscriber

  Reply # 1512738 14-Mar-2016 09:24
Send private message

Clima:
RunningMan:

 

So were you running VoIP on your ADSL connection, or POTS?

 

It was POTS with the ADSL. I was wondering if this was a common problem on UFB VOIP ?

 

While others have made the differentiation it's important to clarify that your issue isn't specific to USB - VoIP over UFB is either via ONT or RGW, and in both cases there are many variables at play as each RSP has their own RGW's they're deploying and their own softswitch for voice services.

 

Your situation is unique to your RSP and the hardware they're deploying. Other solutions over UFB don't have this issue.

 

 

 

 




67 posts

Master Geek
+1 received by user: 7


  Reply # 1512769 14-Mar-2016 09:47
Send private message

sbiddle:

Clima:
RunningMan:

 

So were you running VoIP on your ADSL connection, or POTS?

 

It was POTS with the ADSL. I was wondering if this was a common problem on UFB VOIP ?

 

While others have made the differentiation it's important to clarify that your issue isn't specific to USB - VoIP over UFB is either via ONT or RGW, and in both cases there are many variables at play as each RSP has their own RGW's they're deploying and their own softswitch for voice services.

 

Your situation is unique to your RSP and the hardware they're deploying. Other solutions over UFB don't have this issue.

 

 

 

 

 

 

Thank you. Do I interpret your comment correctly in that each RSP provides their own 'terminating' equipment , in my case a softswitch and RGW, and therefor the Caller-ID provision is all within their possible control. That would indicate they have chosen incompatible devices with regard to this service.

370 posts

Ultimate Geek
+1 received by user: 203

Trusted

  Reply # 1512809 14-Mar-2016 10:37
Send private message

Hi Clima, looks like you are the first one to report that as an issue. Please log a fault with the helpdesk and the DEV guys will start the process of looking into what's happening there. If it requires a new Firmware build on the NF4V its likely to take a while and not be a quick fix however.


1 | 2 | 3
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.