|
Post by W6KD on Jun 1, 2016 12:44:27 GMT -7
I'd start by switching to another CCS server...704 seems to work better than the default (706) lately. That's done in the gateway config GUI, in the DCS-CCS tab.
Regards
|
|
|
Post by Mark - G0TOV on Jun 1, 2016 12:52:35 GMT -7
If it is of any help, on all of the Commander images I have configured I always set the CCS Server to 01 - seems to work best, in the UK at least. I was led to believe that 05 is UK based but never seems to work for me. A friend of mine uses the Commander image via a DVAP using CCS001 with no issue.
To John - AA7US - Maybe a typo on your part but you show Cxxxxxxxx - I note eight characters, this should be seven, have you added a digit possibly causing you an issue....
Regards Mark. G0TOV
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jun 1, 2016 21:12:08 GMT -7
Thanks guys!
After countless hours of hair pulling and frustration, all it took was changing our CCS7 servers to 704 and we immediately linked!
The next problem is that once we were linked, neither one of us could hear the other. Of course we both switched to CQCQCQ in Your Call after the link was established. We're going to take a break and try again tomorrow after getting some sleep. Maybe the inability to actually TALK was a glitch that'll go away.
73,
John AA7US
|
|
|
Post by Mark - G0TOV on Jun 2, 2016 13:00:16 GMT -7
Hi John, nothing of any value to add I'm afraid that you may find helpful other than a suggestion to try CCS001, I have personally never had any issues using this server, might be worth a try. I'm sure Bob will have some advice though.
One comment I would make, and apologies if you already know this, but always ensure you are Unlinked from any repeaters or reflectors when using CCS otherwise your "private" conversation is relayed across the network to every set of ears that may be listening. Bob has a post entitled CCS A Very Bad Practice, or something similar which explains this. I hope you get sorted soon.
Mark.
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jun 2, 2016 13:40:43 GMT -7
Thanks Mark.
I did read Bob's article and am aware of the huge potential annoyances with direct linking.
I have a lot to learn about direct linking at would like to know more about how to handle a situation where someone suddenly links to me when I'm sitting on a busy reflector in the middle of a net. Since it's never happened to me, I'm not sure what to expect. During the direct link, will I have any indication that I'm still connected to a reflector from my radio?
Also, can you clarify if ircDDB is required for CCS7 routing to work, or can I disable ircDDB to save bandwidth (I'm using cellular Internet)?
Any and all pointers are appreciated.
John AA7US
|
|
|
Post by Mark - G0TOV on Jun 2, 2016 13:55:48 GMT -7
John, If I were to connect to you whilst you are linked for example to a reflector it would announce "Linked to G0TOV" - now, if you wished to talk to me you would need to Unlink from the reflector and then switch to CQCQCQ aka Talk and take up the conversation. With CCS I think the timing is set to 15 Minutes where if there is no activity the network drops the connection and you get a "Not Linked" response. Your only indication that you were still connected to the "busy reflector" is that you are still hearing voices. So for example, the net has finished, the relector is quiet and suddenly you get a CCS connection, my advice is to issue the Unlink command and then go to CQCQCQ to take up with your CCS contact, perhaps work on a "just in case" basis, if you cannot remember previously unlinking then Unlink again, or of course check the status by issuing the "I" command - this will tell you if you are "Linked to...." Or "Not Linked".
As for the IRCDDB connection, I am no expert but I know from experience it uses very little cellular data but is required so that the network knows where the station was last heard and thus knows where to route your CCS connection to, perhaps Bob will advise better than I. I "think" without it you may have some trouble. If you didn't use CCS linking at all then for sure it can be switched off, you would be effectively using cellular data for no reason.
I use an Icom 2820 in my car, with Ras Pi (and Commander V2 of course) tethered to my iPhone - works perfectly. I have IRCDDB on all the time. I hope that may be of some help.
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jun 2, 2016 17:47:53 GMT -7
I hope that may be of some help. Thanks a million for that detailed explanation Mark! You're VERY helpful. I now better understand what to expect when sending or receiving a direct link. Currently I'm using my RasPi-DVAP with an IC-7100 in a base station setup, but I have an ID-51A+ on order so I can use it mobile like you're doing. 73, John AA7US
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jun 2, 2016 20:55:27 GMT -7
Mark,
I have an update...
Tonight I was able to initiate a link to the other station that I'm working by using his CCS7 ID. No problem there.
With both of us switching to CQCQCQ in Your Call, he could hear me just fine when I transmitted but I couldn't hear him when he transmitted. To clarify further, I received no signal when he keyed up. We can converse normally through any reflector we connect to.
Also, he cannot initiate a CCS link to me from his end. He says he gets a "number unknown" error.
We've triple checked that all of our settings are the same in the ircDDB Gateway software in our Pi's (well, as near as we can without sitting beside each other), ircDDB is enabled and working, CCS is enabled, and we're both using server CCS704. BTW, we're both showing up on the "Last Heard" listing on the ircDDB server we're using which is rr.openquad.net (OpenQuad.net).
One additional test we haven't tried is to have him (the other station) try switching to server CCS701.
73,
John AA7US
|
|
|
Post by Mark - G0TOV on Jun 2, 2016 23:55:15 GMT -7
Hi John, no problem, happy to help with what little knowledge I have. this is a little strange though, your number 3153193 is valid and assume his is also a valid CCS7 issued ID too - I know on some of the DCS reflector dashboards I have seen the note "No CCS No Voice" . The way I use this, not sure how you are both doing it but maybe worth checking, for me to connect to you for example I would issue C3153193, once I hear Linked To AA7US I would switch to CQCQCQ (Talk, as I have programmed) as would you and the conversation goes ahead, when we had finished I would issue CA and the connection would be Unlinked. The issue you are having seems to be the routing of the audio which as Bob has stated doesn't need any special setup whilst using the Commander image - I'm at a slight loss as to what this could be, I'll consider it more.
As for the 51, excellent little radio, I have the E version - the screen was just too small for use in my car for me, too dangerous to change memories whilst moving ! If you are intending programming it I recommend RT Systems software.
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jun 13, 2016 8:44:41 GMT -7
I have an update on this problem...
With help of another ham experienced with callsign routing using CCS7 through an RPi and DVAP, additional testing revealed the exact problem seems to be, that even after two weeks of waiting, my CCS7 ID is not yet properly mapped to my callsign in the CCS database used with D-Star. Currently I can link outbound to other CCS7 users, they can hear me when I transmit, but they can't connect back to me which means I can't hear them. Examining ircDDBGateway log files revealed I'm coming up as an "unknown" user.
And I'm not alone. I checked other CCS7 ID's issued about the same time mine was and they're also coming up as unknown users.
73,
John AA7US
|
|
|
Post by Mark - G0TOV on Jun 13, 2016 11:24:50 GMT -7
Hi John, so it was as I eluded to then, no valid CCS ID no voice ! I emphasise the word "valid" meaning not yet completely setup. In the UK this registration happens very quickly, certainly within 24hrs, seems strange this is taking so long for you. Maybe email the registration admin to ask why. Sounds like you are getting there which is great - good luck. Mark
|
|
|
Post by km4rzt on Apr 23, 2017 8:06:57 GMT -7
I have an update on this problem... With help of another ham experienced with callsign routing using CCS7 through an RPi and DVAP, additional testing revealed the exact problem seems to be, that even after two weeks of waiting, my CCS7 ID is not yet properly mapped to my callsign in the CCS database used with D-Star. Currently I can link outbound to other CCS7 users, they can hear me when I transmit, but they can't connect back to me which means I can't hear them. Examining ircDDBGateway log files revealed I'm coming up as an "unknown" user. And I'm not alone. I checked other CCS7 ID's issued about the same time mine was and they're also coming up as unknown users. 73, John AA7US I know this is an old thread but a friend of mine is having this same problem. He can connect to me and we can talk. When we unlink and I try and connect to him, the log file states that his CCS ID cannot be mapped to a call sign. Did you fix your problem? If so, how? Thanks in advance for any advice.
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Apr 23, 2017 8:11:07 GMT -7
I know this is an old thread but a friend of mine is having this same problem. He can connect to me and we can talk. When we unlink and I try and connect to him, the log file states that his CCS ID cannot be mapped to a call sign. Did you fix your problem? If so, how? Thanks in advance for any advice. Unfortunately, I never found a fix and finally just gave up on ever getting CCS7 linking to work for me. 73, John
|
|
|
Post by km4rzt on Apr 23, 2017 8:13:35 GMT -7
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Apr 23, 2017 8:26:25 GMT -7
Yes and no response. I sent emails to everyone I could find associated with the registry... no response from anyone. However, I have a sneaky suspicion the problem is actually a port forwarding problem (i.e.: blocked ports) and not a registry problem. It's going to take someone with a lot more time, equipment, and willingness than me to investigate this possibility. John
|
|