OMS Compressors

[Medbck]

Hi everybody,

I manage a virtualized lab with OXE and OMS (OXE R11.1 L1.301.28b and OMS 3.06).
The OMS is in service, I manage it in the shelf n°5, and I manage 30 compressors for IP devices.
Actually I try to establish a call between an IP-Phone and a SIP phone. from sip to IP phone, calls are OK. but in the other side (from IP phone to SIP Extension), the ring is ok, but as soon as i hang up I get please go on hook

Can you please help me to resolve this issue.

Thanks by advance.

[tot3nkopf]

SIP phone defined as SIP extension or SIP device in OXE. If SIP device, is the SIP trunk group defined (as stated in the docs)?

Check also the codecs. You can use represent to check if the OMS takes part of the communication or compvisu to check compressor usage.
SIP traces would be of help also.

You did not provide us anything (traces, configuration...). Just guessing above to try to help you....

[Medbck]

Thanks for your answer.
Sorry for not given traces, here after some détails:
SIP phone is deefined as sip extension.
I tried using compvisu but no compressor was used, and I guess that OMS doesn't take part of communication.
here after a sip trace when trying to establish a call from IP phone (dir: 20001) to the SIP extension (10054):

(191779:000072) +------------------------------------------------------------+
(191779:000073) | Message sent UA (neqt : 1850-1) ----> SIP
(191779:000074) | INVITE : 10054@lab-optimus:5060 ; user=phone
(191779:000075) | From : <20001> 20001@192.168.50.40:5060 ; user=phone
(191779:000076) | To : <Room 54> 10054@192.168.50.40:5060 ; user=phone
(191779:000077) +------------------------------------------------------------+
(191779:000078) | SDP :
(191779:000079) | @IP:port = 192.168.50.160:32514
(191779:000080) | ALGOS :
(191779:000081) | PCMA
(191779:000082) | DTMF : 97
(191779:000083) | DIRECTION : SEND & RECEIVE
(191779:000084) | cac : false
(191779:000085) | Allow_UPDATE: 1
(191779:000086) | autoAnswer : false
(191779:000087) +------------------------------------------------------------+
(191779:000088) SIP : Global_get_mcdu, in dico
(191779:000089) SIP : Global_get_mcdu, in dico
(191780:000090) +------------------------------------------------------------+
(191780:000091) | Message received SIP ----> UA (neqt : 1850-1)
(191780:000092) | Informational 180
(191780:000093) | RELATIVE REQUEST : INVITE
(191780:000094) | Allow_UPDATE: 0
(191780:000095) | No SDP
(191780:000096) | COLP
(191780:000097) | COLP
(191780:000098) +------------------------------------------------------------+
(191801:000100) +------------------------------------------------------------+
(191801:000101) | Message received SIP ----> UA (neqt : 1850-1)
(191801:000102) | Successful 200
(191801:000103) | RELATIVE REQUEST : INVITE
(191801:000104) +------------------------------------------------------------+
(191801:000105) | SDP :
(191801:000106) | @IP:port = 192.168.50.103:10026
(191801:000107) | ALGOS :
(191801:000108) | PCMA
(191801:000109) | DIRECTION : SEND & RECEIVE
(191801:000110) +------------------------------------------------------------+
(191801:000111) +------------------------------------------------------------+
(191801:000112) | Message sent UA (neqt : 1850-1) ----> SIP
(191801:000113) | ACK
(191801:000114) +------------------------------------------------------------+
(191801:000115) event_init_screen_mem : line 1 tscreen '20001
'
(191801:000116) event_init_screen_mem : line 1 tscreen 'Room 54
'
(191801:000121) event_init_screen_mem : line 1 tscreen '20001
'
(191801:000122) Switch_Tab neqt(1850) tab(1) indch(145)
(191801:000123) Switch_Tab CHANSIP(145) is already the first one return OK
(191801:000124) +------------------------------------------------------------+
(191801:000125) | Message sent UA (neqt : 1850-1) ----> SIP
(191801:000126) | BYE
(191801:000127) +------------------------------------------------------------+
(191801:000128) event_init_screen_mem : line 1 tscreen '20001
'
(191804:000129) +------------------------------------------------------------+
(191804:000130) | Message received SIP ----> UA (neqt : 1850-1)
(191804:000131) | Successful 200
(191804:000132) | RELATIVE REQUEST : BYE
(191804:000133) | No SDP
(191804:000134) | CSTA_index : 9
(191804:000135) +------------------------------------------------------------+
(191809:000136) event_init_screen_mem : line 1 tscreen 'Please go on hook
'
(191823:000138) event_init_screen_mem : line 1 tscreen 'Please go on hook
'
(191823:000140) event_init_screen_mem : line 1 tscreen 'Please go on hook
'
(191823:000142) message_enregistrement() box_state=6 ML_NOT_MSG=6
(191823:000143) message_enregistrement() mess_enreg=0 autre_mess=0

if you need more traces please let me know which one you need.

Thanks a lot

Regards

[Medbck]

Hello again,
I find the issue, As I'm using Telematrix 9602 sip extensions, by default they have dtmf payload to 101 and the call server has this parameter to 97. so we have to change it from one side to adapt it.


Thanks for your assistance

[cccengg]

Hi

i want to install the OXE-MS in the virtual machine.

i m getting hardware compatibility , key board error its not going on and quieting the installation.

Any idea would be a great help

[cccengg]

oms5.jpg

oms4.jpg

oms3.jpg

oms2.jpg

oms1.jpg

oms6.jpg

Hi CHAMPIONS

i want to install the OXE-MS in the virtual machine.

error pix are attached.

Any idea would be a great help

REGARDS

[tot3nkopf]

Can you post your VM configuration?

Equivalent for:

Capture.JPG

[cccengg]

Re: OMS Compressors
Report this post Quote
Post by tot3nkopf » Today, 00:31

Can you post your VM configuration?

HI , Sure ,,,, my both virtual machines ,,, 1) Diployment VM 2) OMS VM Photos are attached.

[tot3nkopf]

With show all devices do you see any Keyboard driver in VM settings?
What was the type of OS that you have chosen when you have created your VM?
Did you checked the checksum for both images?

[cccengg]

Re: OMS Compressors
Report this post Quote
Unread post by tot3nkopf » 37 minutes ago

With show all devices do you see any Keyboard driver in VM settings?
What was the type of OS that you have chosen when you have created your VM?
Did you checked the checksum for both images?

i am showing u the configuration photo where the key board was selected.

and how to check the checksum of the images? any idea