Discussions (English)

Registered 4 years 326 days

Alejandro 5047 Thursday, 16 July 2020, 12:13 PM

MOH - Call release

Hello,

I am Alejandro, from Voicelan, Ascom.

I have a problem in one customer that I don't know how to solve.

When I receive a call from the ISDN and I place it on hold from the IP phone, then I get a call release and the call is ended in both ways.

The scenary is as follow:

PBX IP800 (tried to do this with an IP411 and same results)
PBX connected to PSTN thru an ISDN network.
Ascom IPDECT phones registered in IP800
Yealink IP phones registered in IP800
MOH URL (PBX - Config - General): http://192.168.42.131/DRIVE/CF0/my_announcements/music.$coder?coder=g729,g711a,g711u,g723&repeat=true

The problem occurs exclusively when I receive a call from the ISDN and I place it on hold from the Yealink IP phone, then I get a call release and the call is ended in both phones.

It does NOT OCCURS when the call is made from the Yealink to the ISDN. In this case the MOH is works without problem.

For internal calls there are not troubles, the MOH is ever heared.

Traces from IP800 syslog:

CAFETERIA 621 is the IP phone

10 is the external ISDN number

EXTERIOR is the extern Gateway to route incoming and outgoing calls.

(rember that always is the IP phone registered in IP800 who puts the call on hold)

CALL FROM ISDN TO YEALINK IP-PHONE = NOK

20200716-113123 PBX0 3 _MOH_() <-setup ()

20200716-113123 PBX0 1 CAFETERIA(621:621) hold-> (10)

20200716-113123 PBX0 3 _MOH_() conn-> ()

20200716-113123 PBX0 1 CAFETERIA(621:621) rel-> (10)

20200716-113123 PBX0 2 EXTERIOR(10) <-rel CAFETERIA(621:621)

20200716-113123 CALL 1 B:Rel 10->20 G729,30sx(0,0,0)/G729,30sx(0,0,0) TEL1:10:->GW1:621: Cause: Normal call clearing

20200716-113123 PBX0 2 EXTERIOR(10) rel-> CAFETERIA(621:621)

20200716-113123 PBX0 3 _MOH_() <-rel ()

20200716-113123 PBX0 3 _MOH_() rel-> ()

20200716-113123 CALL 1 A:Rel 10->20 G729,30sx(0,0,0)/G729,30sx(0,0,0) TEL1:10:->GW1:621: Cause: Normal call clearing

20200716-113123 CALL 1 Free

CALL FROM YEALINK IP-PHONE TO ISDN = OK

20200716-113607 PBX0 3 _MOH_() <-setup ()

20200716-113607 PBX0 2 CAFETERIA(621:621) hold-> (10)

20200716-113607 PBX0 3 _MOH_() conn-> ()

All test are done with the Innovaphone in Test mode to avoid license problems.

I don't know where can be the difference between calling from IP800 or receiving the call.

For internal calls there are not troubles, the MOH is ever heared.

I hope you can help me. If you need more information, just ask for it.

Attached the config file of the IP800.

Thank's in advance.

Best regards,

Alejandro

standard-IP800-06-32-b4.txt

Registered 8 years 174 days

Muschelpuster Friday, 17 July 2020, 08:56 AM

Re: MOH - Call release

I'm pretty that this is not a MOH-problem. You can delete the MOH-URL temporally to verify this.

Niels

Registered 4 years 326 days

Alejandro 5047 Friday, 17 July 2020, 12:16 PM

Re: MOH - Call release

Hello,

Thank you for your answer but, if I delete the MOH URL the phone holds without problem in any case.

I tried to do this with all avialable códecs, with hold signaling inactive, sendonly and sendonly with 0.0.0.0. I discard códecs problem because, as I said in the first post, the problem only occurs in one way, from ISDN to Yealink. However, if is from the Yealink to the ISDN the MOH works correctly.

I think I have done all the possible tests, although I have some experience with Innovaphone (I am Ascom distributor and Ascom always works with Innovaphone PBX), I'm not an Innovaphone expert.

I am using Yealink as desktop IP phones because these are the phones that has my customer and, as far as I know, this manufacturer is certified by Innovaphone.

I don't know what more to do...

Thank you in advance!

Regards,

Registered 8 years 174 days

Muschelpuster Friday, 17 July 2020, 12:49 PM

Re: MOH - Call release

Ok, and what is the exact setup? The phones is in the same IP net like the PBX, or is the a reverse proxy or other NAT or firewalling involved?

Niels

Registered 4 years 326 days

Alejandro 5047 Friday, 17 July 2020, 02:14 PM

Re: MOH - Call release

Hello,

All devices are in the same network, all connected via LAN. The phones are configured by DHCP.

There are no firewalls, VLANs or proxies between the phones and the PBX. All are inside a simple LAN connected to the same unmanaged switch.

In the customer site:

Innovaphone IP800 with fixed IP add: 10.10.10.10 /24

Desktop IP phones with DHCP range: 10.10.10.100-200 /24

Gateway: 10.10.10.1 /24

In my demo lab:

Innovaphone IP800 with fixed IP add: 192.168.42.131 /24

Desktop IP phones with DHCP range: 192.168.42.30-90 /24

Gateway: 192.168.42.254 /24

Thank's,

Alejandro

Registered 8 years 174 days

Muschelpuster Monday, 20 July 2020, 06:59 AM

Re: MOH - Call release

Ok, I drop. I have no More ideas.

Niels

Registered 4 years 326 days

Alejandro 5047 Tuesday, 21 July 2020, 12:10 PM

Re: MOH - Call release

Good morning,

Thank you very much for your time Niels.

Finally I found the problem.

The Gateway I have configured in my Innovaphone to route the calls, had activated the RTP Encryption (this parameter is set by default).

It is no matter for my Ascom phones for example, but for the yealink it was a problem. If I don't say to the Yealink phone that exists an SRTP encryption, the innovaphone gateway automatically release the call, because the sent data was not encrypted, it should be a security policy.

My choice was to disable the RTP encryption from the IP800 gateway, however, it could be enabled in the phones (in Yealink settings: Account - Advanced - RTP Encryption (SRTP) = Optional)

I know I am not in a Yealink forum, sorry, but I think it can be helpful for some people because this parameters are default settings for Innovaphone but in the most case of SIP phones (not only Yealink) it is usally disable, and could affect, not only to the music on hold, also to other RTP data.

Hope it can help.

Alejandro

You are here