5624 hold rejected

[floppy1]

Hi

MiVb 9.3 on MXe111 controller
MiCollab 9.7 on VM integrated MBG

We have registered 5624 phones via the MBG internal IP address in order that the call recording equipment can capture the audio via the SCR taps.

Since doing this placing a call on hold from the 5624 phones fails and "hold rejected" is displayed on the phones. This is only on outbound calls incoming calls can be placed on hold and a supervised transfer can be made successfully.

I have looked at and changed some settings on the SIP peer profile such as avoid signalling hold to peer and some COS options local MOH , NO MOH on transfer and so on but no change.

The SIP trunks are not being proxied on the MBG and perhaps this has something to do with it ?

Any ideas suggestions or if you have had this issue please advise.

I may be able to get some call traces and I suppose this may shed some light on the matter but it is difficult to get traces from the site at the moment.

Thanks

 

[Billz66]

so prior to them being registered to the MBg they were able to put calls on hold?

whats the MBg streaming address set to ?
whats the SIP settings set to on MBG - any local streaming enabled

cant recall whether MBG on micollab is supported for SRC tapping
definitely not if there is a public address set as the MBG streaming address

- you may need a seperate lan only mbg to use for SRC tapping

If I never did anything I'd never done before , I'd never do anything.....

 

[floppy1]

Billz66, thanks for your reply.

This really came to light as the users like to use supervised transfers and this was displaying hold rejected when attempted. Interestingly they can do a blind transfer so that it what there doing at the moment.

Yes prior to registering the 5624 sets with the MBG they could place calls on hold and do a supervised transfer on both incoming and outgoing calls. Now call hold only works on incoming calls ?

The MBG does have an external IP address as there are MiCollab mobile softphones programmed on the system set as teleworker devices.

The LAN side streaming is the internal IP address of the MBG and the WAN side is the public IP address and the call recording does work. Also the binding IP addresses are the same LAN = LAN and WAN = WAN

I seem to recall in the past seeing something about having to have a LAN MBG for call recording but this config does work with call recording and Mitel TS did not note it as being an issue when we were helping us to get the 5624 sets registered on the MBG " that's another story "

No local streaming as docs do say that call recording wont work if on although I believe in the next release this wont be the case.