PAP2T Caller ID - OK with 2talk not with Orcon Genius

Forums › VoIP › PAP2T Caller ID - OK with 2talk not with Orcon Genius

Frankiej45

21 posts

Geek

#143644 22-Apr-2014 12:47

Hi all,

Having followed lots of useful info already found on the forums, I now have 2 VOIP lines active on my PAP2T - one for 2talk and one for Orcon Genius. Both lines work fine for making and receiving calls, and both work fine for outbound caller id. However only the 2talk one correctly displays incoming caller id. On the Orcon Genius line no caller id is displayed at all for an incoming call.

My PAP2T is setup using the regional settings for NZ as per the guide on this forum - and both lines have the callerid service enabled.

When i use the original Orcon Genius modem I do get caller id successfully. Just I would much prefer to use my PAP2T and my more capable router / modem.

Any thoughts on where I should be looking in the PAP2t config to help fix this?

Thanks in advance!

chevrolux

4962 posts

Uber Geek
Inactive user

#1029103 22-Apr-2014 13:14

I would be checking your impendance and FSK settings.

Go to Admin login and then Advanced view. Go to 'Regional' and shoot down to the bottom 'Miscellaneous' settings.

FSK should probably be set to the 'bell' standard.

Although if it works on the 2Talk line then probably won't be those settings as they are 'global' for each FXS port.

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

Frankiej45

21 posts

Geek

#1029113 22-Apr-2014 13:33

Thanks for the response - is is set to the bell standard. As you say, given it works for 2talk and the settings are global - my assumption has been that the regional settings should be ok.

coffeebaron

6212 posts

Uber Geek

Trusted

Lifetime subscriber

#1029147 22-Apr-2014 14:34

Work through the alternate FSK settings in case Orcon use something non-standard.

Rural IT and Broadband support.

Broadband troubleshooting and master filter installs.
Starlink installer - one month free: https://www.starlink.com/?referral=RC-32845-88860-71
Wi-Fi and networking
Cel-Fi supply and installer - boost your mobile phone coverage legally

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

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

#1029152 22-Apr-2014 14:41

coffeebaron: Work through the alternate FSK settings in case Orcon use something non-standard.

FSK is analog side, not SIP side, so that doesn't make sense :/

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1029153 22-Apr-2014 14:42

The FSK settings only determine the CID format used on the FXS port (ie the analogue phone) so changing these won't have any impact other than breaking all CID from working. CID from Orcon is sent in the SIP header.

old3eyes

9112 posts

Uber Geek

Subscriber

#1029304 22-Apr-2014 19:10

If it's anything like 2Talk and Orcon SIP trunks. 2Talk sends the nation number as CLID i.e 095551212 where as Orcon just sends 95551212.

Regards,

Old3eyes

coffeebaron

6212 posts

Uber Geek

Trusted

Lifetime subscriber

#1029391 22-Apr-2014 20:17

Have you swapped phones between ports to rule out handset issue?
Swapped line configs around to rule out ATA port?

Rural IT and Broadband support.

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

chevrolux

4962 posts

Uber Geek
Inactive user

#1029398 22-Apr-2014 20:35

old3eyes: If it's anything like 2Talk and Orcon SIP trunks. 2Talk sends the nation number as CLID i.e 095551212 where as Orcon just sends 95551212.

Shouldn't really matter though how it arrives though I wouldn't have thought.

Wouldn't the ATA just grab it off the SIP packet and convert it to FSK signals?

Frankiej45

21 posts

Geek

#1029400 22-Apr-2014 20:38

Its actually the same phone, it has 2 line ports. One connected to line 1 on pap2t and the other connected to line 2.

I have just tried reversing the connections and also reversing the line setup in the pap2t.

Same problem.

Are there any other pap2t settings that could affect this? I'm not sure which other ones are worth altering?

Thanks for the responses so far!

old3eyes

9112 posts

Uber Geek

Subscriber

#1029548 23-Apr-2014 08:33

chevrolux:
old3eyes: If it's anything like 2Talk and Orcon SIP trunks. 2Talk sends the nation number as CLID i.e 095551212 where as Orcon just sends 95551212.

Shouldn't really matter though how it arrives though I wouldn't have thought.

Wouldn't the ATA just grab it off the SIP packet and convert it to FSK signals?

No. The CPE must be able to insert the leading zero. With PBX systems the incoming invite message gets modified and the leading zero inserted. With an ATA I suspect it can't be done. In the Telecom NZ analog world they just send 95551212 but the CPE i.e. your fone at home is preprogrammed to insert the zero. If you were to use one of these preprogrammed fones on a 2Talk line you would get 0095551212. Been there done that..

Regards,

Old3eyes

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1029622 23-Apr-2014 09:57

Analogue phones in NZ must be capable of inserting a leading 0 to get PTC approval. The "standard" for CID in NZ on analogue and ISDN lines excludes the 0 as 0 is simply a network access code and not part of the phone number.

In the VoIP world it's typically not possible to do this on a VoIP phone unless you've got a PBX so most VoIP providers either send numbers with the leading 0, send numbers in full E.164 format or give you the option of how you want to receive the number.

Frankiej45

21 posts

Geek

#1030112 23-Apr-2014 21:04

From some of the discussion that has taken place - I have one idea as to why it may not be working - would be keen to get your views.

I believe that the CID is sent between 2nd and 3rd ring? At the moment I've noticed that if I call the Orcon line from my mobile, i hear 2 rings before anything happens on my phone at home - the home phone only starts ringing on ring number 3. So presumably that means that the phone may well not be getting the CID at all?

Does that seem likely and if so is there anything that could be tweaked that could fix the cause of the phone taking so long to start ringing?

old3eyes

9112 posts

Uber Geek

Subscriber

#1030298 24-Apr-2014 08:51

CLID is normally sent at the end of the 1st ring cycle in the analog world, in the SIP works it's sent as a part of the inbound invite message...

Regards,

Old3eyes

Frankiej45

21 posts

Geek

#1030783 24-Apr-2014 20:08

Well the good news is I've finally fixed it!

Turned out that I had a stun server setup and removing that means the phone now rings instantaneously and also the caller id now works!

Thanks for the help all