Recent content by Striep

Hello Janni78, i just have the TA3200 and no other diveces with me. I changed the config so the TA3200 looks to the "invite" field and it works fine now. I still belief it isn't correctly send from the ip office. Thanks for now, i will close this thread.

It isn't going wrong in the TA3200, see the uploaded picture of the trace

Hello outthere, I have the following issue: On headoffice is a 500V2 running 9.1.7.0.163. On 4 other locations is a Yeastar TA3200 media converter installed to conect the extension on site witch are connected with old wiring. Sip extension 51813 has a forward on no answer and on busy set to sip...

is there anyone active in this forum?

Hy guys, i have done some testing yesterday and finaly got it working. First of all, my collegue who was first working on this issue pointed me in the wrong direction. I first looked with the SSA tool what the extension was doing making an external call. Then i found out that there was a short...

I'll give it a shot

they are short on DDI numbers. So there are several extension numbers who won't match they DDI range.

so what you are saying is for example a ddi range of 0771234560 to 0771234569 an extension with internal number 4562 has the right outgoing CLI. A extension with internal number 3333 and a feature access code ? => .s771234568 won't work??

Actualy, i think the ipo does something with it.... i can upload a cfg if you want to check the configuration

They allow that method. A DDI number in the incomming call route who matches a extension number gives the correct cli to a outgoing call...

Hello janni78, In the Netherlands the providers expect 9 or 10 digits. I have tried both with a valid DDI number, but still it sends the primary CLI number...

We have 2 customers, both using a PRI. On both systems the extension numbers are equal to the last 3 or 4 digits of the DDI number. An extension who's extension number isn't equal to a number in the DDI range now sends the primairy number of the DDI range. Even if i program the extensions...

Problably your dect licence contains not more than 2 base stations. Probably you have to upgrade your dect license from 2 to 3 and then it will work oke.

We have occured other problems in the combination of 4.0.10 IPO and 4.0.18 VMPro. Maybe the combination isn't stabel. We made a case to Avaya, but no responce since then....

Maybe you can solve this with twinning?? You can program an pot port to a digital port. Or program a collative huntgroup with a digital and pot port in it.