Magix R4 v.7 caller id

[engofwbs]

I have magix r4 v.7 with
2 of 408 gs/ls/mlx cards
1 of 408 gs/ls - id - mlx card
mlx-10d phones


I hooked 4 vonage lines to the gs/ls-id-mlx card(loop-start)
and already set the toggle button

There no caller id appears but the name of the line...

does anyone know what my problem is?
please help me...

 

[Dexman]

Do you get the Caller ID info if you connect a typical consumer telephone to the Vonage box?

If you connect the system to a real POTs line with Caller ID, does the info appear on the display?

If it ain't broke, I haven't fixed it yet.

 

[merlinman]

Did you set Loop Start Caller ID Delay?

http://home.comcast.net/~merlinman

 

[engofwbs]

Yes, I tried with normal CID phone directly to the vonage box and it worked...

I already set Loop Start Caller ID Delay...

 

[MrTelecom1]

Yeah, I agree on the Loop start delay.
If they answer to quickly it's just not gonna be there!

MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!

 

[tdaugirdas]

Vonage lines will NOT show Caller ID when connected to a Magix PBX - with one exception - a Vonage line to Vonage line call. What I do is just connect a Y with a cheap caller ID box for each Vonage line. That is the only way you will get caller ID.

If you want to experiment - call one of your Vonage lines from one of the other Vonage lines - and the caller ID info should display - just remember that a Vonage line only shows caller number - not Name.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[MrTelecom1]

So I gotta ask, Why Doesn't it show on a magix?
Is the format of Vonage CID delivery just incompatible?

If a small CID box works on it, why wouldn't it be avail on an "ID" card in the magix?

...and it only shows Data on/from another vonage call.., so only switches in their network deliver caller ID to each other and not the PSN? I think I'm glad I never opt to try it.

I Love my Copper Lines ... They just work.



MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!

 

[tdaugirdas]

Don't know why Vonage Caller ID does not work on a Magix PBX - and neither does Vonage - although I went through extensive attempts with their Tier 3 engineers to make it happen about 18 months ago - with no success. I hear through the grapevine that their signal is just "too dirty" for the Magix to interpret the CID data - even though a $10 CID box has no trouble. I have a Vonage "local" number in Mexico City - and whenever that number is dialed and rings on my Magix system - I do see the Mexico City phone number show up. On rare occaision I see other caller ID info or partial info - but usually I see nothing. Vonage CID does seem to work OK with an IP Office PBX - except that a reliable disconnect signal when a calls go to voicemail - can get stuck and tie-up the Vonage trunk.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[phonesrus]

As We ALL know, Modem calls over IP don't work worth a damm. CallerID is a modem signal burst sent after the first ring sequence. When it hits a POTS endpoint(PBX)it may, or not, be distorted depending on the quality of the signal compression and packetization as it passes thru the router IP gateways, since it is a tonal signal of very short duration (1200 baud). DTMF is also a tonal signal but of longer duration (100 ms)and is easier to handle.
As Tom said an IP to IP CallerID usually works because it is using the same standard of compression, beginning to end, and of course the particular carrier always wants their stuff to work better.
Cheap CID boxes are built to more lax standards than a Good PBX and may therefore be able to read a "dirty" signal better.

 

[MrTelecom1]

Vonage and their Dirty Lil Signal. Somehow I knew I wasn't missing anything to seriously fun...


MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!

 

[tdaugirdas]

Well - except for the fact that Vonage is pretty cheap for long distance - especially if you make lots of calls in the US, Canada and Europe (basically free). And I really like the "local" numbers you can have anywhere in the world for $5 per month. So - I guess I can forgive them for outputting crappy caller ID info. I am about to move my Vonage line to an IP Office anyway - so I will get my Caller ID info to work - now if only I could get IP Office to work correctly with my no-longer-supported TransTalk 9040 - oh well - you can't win them all.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[MrTelecom1]

Yes, the Local number (anywhere almost) is a great thing.
I'm sure with enough twists & tweaks it'll work on an IP office... and ahhhh, the ol' 9040. I used one for a Long time. It was a great cordless. It had surprising distance, especially compared to the crappy previous version 9031 and WORST- the 9030... o'well, those are all dark ages..
What about the later replacement, the model slippin my mind right now .. I was just going to get one myself to replace the 9040 I had that got crushed to many Lil pieces..
O well, off to the Bar-B .. grillin time!

MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!

 

[tdaugirdas]

DON't get the piece of crap replacement for the 9040 - they are virtually useless - with a range of maybe 125 feet - if you're lucky (3810 and 3910). Get yourself another 9040.

Tom Daugirdas,
President
STCG, Inc.
stcg.com