dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
8
share rss forum feed

garys_2k
Premium
join:2004-05-07
Farmington, MI
Reviews:
·Callcentric

1 recommendation

reply to garys_2k

Re: [CallCentric] SOLVED! CC Settings on PAP2T

Click for full size
Original setting, reboots continually
Click for full size
New setting, no more reboots!
After lurking on the threads about the 3CX SIP client I noticed discussion about using the SRV settings and how the SIP port should be set to "0." Hmm, maybe there's something analogous on the PAP2T.

The first graphic is really a closeup of the first one in the original post. Note that I was setting the SIP port while using SRV settings lower down. Apparently that combination causes reboots.

The second pic shows all other settings the same except the SIP port was just NOT specified, the box was left blank. Since I made that change and enabled the line I haven't see a restart in over 12 hours.

Why does this work? Who knows, the PAP2 has bugs, this is one of them. I hope it helps anyone else working on this...

Mango
What router are you using?
Premium
join:2008-12-25
www.toao.net
kudos:15
I checked the admin guide and there is no mention of how the device should behave if SIP Port is blank.

I blanked my own and it defaulted to 5060. Anyone have a theory as to why this solves the problem?


Davesnothere
No-BHELL-ity DOES have its Advantages
Premium
join:2009-06-15
START Today!
kudos:7

1 edit
said by Mango:

I checked the admin guide and there is no mention of how the device should behave if SIP Port is blank.

I blanked my own and it defaulted to 5060. Anyone have a theory as to why this solves the problem?

 
Note that the SIP Port number is BLANK in my screenshot in the OP.

»CallCentric Linksys ATA Screenshots

Not sure of the significance, but I had decided on that setting thru a combination of learning previously what worked for Anveo, and from some other folks' advice about CallCentric, given just before I started the thread, but leaving that field blank was for some other reason (which I cannot recall ATM), rather than to solve any PAP2T ATA spontaneous reboots, as only some of the OBI ATAs had been rebooting as of then, IIRC.

garys_2k
Premium
join:2004-05-07
Farmington, MI
Reviews:
·Callcentric
said by Davesnothere:

said by Mango:

I checked the admin guide and there is no mention of how the device should behave if SIP Port is blank.

I blanked my own and it defaulted to 5060. Anyone have a theory as to why this solves the problem?

 
Note that the SIP Port number is BLANK in my screenshot in the OP.

»CallCentric Linksys ATA Screenshots

Wow, now I recall seeing that and I missed duplicating it, nice job. It sounds like if I'd just followed it my problems would have been fixed days ago. Thanks!


Davesnothere
No-BHELL-ity DOES have its Advantages
Premium
join:2009-06-15
START Today!
kudos:7

4 edits
 
said by garys_2k:

Wow, now I recall seeing that and I missed duplicating it, nice job. It sounds like if I'd just followed it my problems would have been fixed days ago. Thanks!

 
Or might never have happened ?

That's K00L !

Now I cannot say whether or not the random ATA rebooting would have happened to me too - as I had already chosen the blank field for other reasons, and had not anticipated the rebooting.

And if it had anything to do with CC's longer DNS records - not sure either, but they have shortened them again since then.

As I might have also said earlier, trying the blank port was an idea which I first got from learning about DNS records stucture when DNS SRV is being used (while setting up my Anveo account - and had applied the setting first THERE, and later to CC), because a port number usually gets specified for each server in a DNS SRV enabled DNS record.

I think that what may happen is that the port specified in the DNS record may conflict somehow with the port which we enter manually into the ATA.

garys_2k
Premium
join:2004-05-07
Farmington, MI
Reviews:
·Callcentric
said by Davesnothere:

 
I think that what may happen is that the port specified in the DNS record may conflict somehow with the port which we enter manually into the ATA.

Yes, and that caused the (IMHO) buggy code running the PAP2 to reboot the device. Nice that a port conflict caused the equivalent of suicide, but whatever, it's an end of life device.

Just before the DDoS fun started I bought a Obi 100 intended to take over for the PAP2T, thinking I could get GV as a backup and it would be supported for the medium/long term. I did get GV working on it, but now I'm not sure I want that to be part of my backup plan, or how to use it.

I guess I see CC as my primary (now it's back to full use, my home phones are using it ONLY with no forwarding), CWU became my outbound backup (as CID could be set to my "real" number), and GV as a third tier. But that's three lines and each device can only use two at a time.

Anyway, glad to have the PAP2 working again with CC! The little we've used it has been back to its previous level of greatness.