Created by: Abdul Rasheed on 23-01-2012 05:51:50 AM Hello, My name is Abdul Rasheed, i am working on a voice recording solution using SIP trunk and BIB. It was noticed that while running the solution for 1 or 1.5 months in one site, the recording will suddenly stop and when i checked it was found that after the ACK is recieved from CUCM , it will immedietly send a BYE closing the session and the reason for the BYE is Q.850 Cause =65 when i checked i found that the cause=65 means "bearer capability not implemented" i am not sure why this error coming up immedietly on a working system after running for 1.5 months. Is there any thing in CUCM configuration should i verify ? Thanks and Regards Abdul Rasheed
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: Abdul Rasheed on 09-02-2012 03:48:19 AM Hello, can anybody tell me some reasons for the above error. Why does a SIP message get a Q.850 cause =65 (bearer capability not implemented) error?
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: Abdul Rasheed on 19-02-2012 01:52:03 PM Hello Everybody , For the recording using BIB and SIP trunk, the rejection of INVITE messages with a BYE of reason "Bearer capability not implemented" what does this stands for ? THis is not happening always, but at sometimes only. Please let me know if anybody has got the same error and the possible reason . it will be a great help for me Regards Rasheed
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: Ahmed Fayomy on 24-02-2012 07:43:47 AM Hello Abdul Rasheed;
i have the same bye message with the same reason, but my case is 1- SIP Trunk send me the invitations 2- my sip server response with 200 ok 3- SIP Trunk sent to my ACK 101 then he sent to me bye message and he cotinue in sending it.
i read about that my 200 ok response for the invitation should have the SDP and codecs, and if these codecs are not compatable with cucm you will get that bye message.
my case is
1- i created SIP Trunk and give it my pc ip. 2- i run my sip application on my pc . 3- i got two invitations for the call on ip phone with automatic recording 4- i sent 200 ok for these two invitations 5- cucm sent me ack 101 6- cucm continue sending me bye message .
please if you ses that i missed any thing here, like should i configure any thing in network or in my sip SAILFIN server or in CUCM configurations, tell me please, Thanks,
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: Abdul Rasheed on 28-02-2012 11:42:12 AM Dear Ahmed, You have missed out a few messages during your SIP negotitations. You need to go through the SIP trunk messaging guide available in the CDN website to implement those messages.
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: Ahmed Fayomy on 28-02-2012 04:51:45 PM thanks Abdul Rasheed for your reply, now it is working, and the rtp streams came to my recorder pc. but my problem is that i do not know how to save these rtp streams as a file [wav or mp3]., so if you know away to do please tell me to study it. thanks again for your help
Subject: RE: SIP trunk - CUCM Rejection of SIP messages Replied by: =?UTF-8?B?7Je07Zi4?= =?UTF-8?B?7IaQ?= on 21-09-2012 04:55:29 AM i`m sorry but
could you show me a your "200 OK" messages?
i have a problem that cm does not send to me a 101 ACK messages
i don`t know what is the problem of my sip messages
Hi,I'm trying to create an event with more than one timezone. API documentation contains the TimeZoneId as part of the schedule node. Is there a way to set the additional 3 timezones via the API? ThanksHP
Hi Team, I am facing one issue in record with confirm element, while we pressing the * start key for repeat the record element options. exit state of this is Max No match, it will take 3s Timeout. is there any possibility to reduce the timeout i...
hello community,I farly new to APIs and Soap. I am trying to get my first script going but i cannot find what wrong am I doing.my web browser keeps throwing this error Fatal error: Uncaught Error: Class 'SoapClient' not found in C:\xampp\htdocs\...