search for: receive_info

...I'm running the latest CVS as of now. I'm getting the error... *CLI> -- Executing VoiceMailMain("SIP/phone1-e0dd", "") in new stack -- Playing 'vm-login' (language 'en') **Here I push a button** May 9 18:26:18 WARNING[98311]: chan_sip.c:5027 receive_info: Unable to retrieve DTMF signal from INFO message from 5e9f165cd1aea27c@159.144.58.141 By re-installing an older (cvs checkout -r v1-0_stable asterisk) version - everything works fine again... thats with NO config changes at all.. Has someone removed some support for the transporting of DTMF (eg,...

...333333@10.22.0.200;user=phone>;tag=000000000000000000007ad91f06 Max-Forwards: 31 To: <sip:123@0.0.0.0;user=phone>;tag=as2283a438 Via: SIP/2.0/UDP 0.0.0.0:5060;branch=z9hG4bK-5764-36A3EE Content-Length: 3 2 10 headers, 1 lines Receiving DTMF! Feb 28 08:27:44 WARNING[9223]: chan_sip.c:6116 receive_info: Unable to parse INFO message from 000000000000000000007ad91f05@cirpack. Content Transmitting (NAT): SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 0.0.0.0:5060;branch=z9hG4bK-5764-36A3EE;received=0.0.0.0.0;rport=5060 From: "test003" <sip:0133333333@10.22.0.200;user=phone>;t...

...detect DTMF. The problem is that there is no normalisation on the content of the sip info frame for dtmf detection. First, asterisk try to detect the header "application/dtmf-relay" and you have the header "application/dtmf" see line 6069 of /channels/chan_sip.c function "receive_info" Second, asterisk use the protocol define by cisco for dtmf sip info. It means it's looking for the word "signal" into the body. in you body, you have only the digits corresponding to the dtmf so asterisk can't find the dtmf. You have to modify the code around the line 6075...

...detect DTMF. The problem is that there is no normalisation on the content of the sip info frame for dtmf detection. First, asterisk try to detect the header "application/dtmf-relay" and you have the header "application/dtmf" see line 6069 of /channels/chan_sip.c function "receive_info" Second, asterisk use the protocol define by cisco for dtmf sip info. It means it's looking for the word "signal" into the body. in you body, you have only the digits corresponding to the dtmf so asterisk can't find the dtmf. You have to modify the code around the line 6075...

...e265f8", "cvb|7572721122|1") in new stack -- Goto (cvb,7572721122,1) -- Executing VoiceMail("SIP/209.96.249.5-41e265f8", "236@cvb") in new stack -- Playing 'vm-intro' (language 'en') Mar 17 13:27:15 WARNING[196620]: chan_sip.c:6116 receive_info: Unable to parse INFO message from CB1DAB05-964911D9-90F293DC-DDF2614@209.96.249.5. Content Note i only started getting the above INFO msg error after i upgraded my cisco IOS to recognize the incoming caller ID name info (before i douln;t see the caller ID name at all), so i suspect thats how...

I'm trying to use early-dial. Here, all hardware PBX have it. You dial numbers and, as soon as you have a matching dialplan entry, you get throught. I my Grandstream I enabled early-dial. And when I put exten=91,1,Milliwatt in my dialplan then it works as expected. Also, when I call other SIP or IAX phones it works. Hurray! But how can I get it working with external lines? In my

...oes not understand this INFO message, so it acts as a UAS instead of proxy. How to let asterisk just forward this request to the other endpoint and instead processing it as a UAS? Thank you, Wei Here is the log from the asterisk server: Mar 17 12:01:31 WARNING[2804]: chan_sip.c:6134 receive_info: Unable to parse INFO message Here is the trace: Frame 96 (808 bytes on wire, 808 bytes captured) Session Initiation Protocol Request-Line: INFO sip:6002@192.168.10.90 SIP/2.0 Method: INFO Resent Packet: False Message Header Call-ID: 60b8596c-4135c-c0a81e68@...

...roxy. > > How to let asterisk just forward this request to the other endpoint and > instead processing it as a UAS? > > Thank you, > > Wei > > > > > Here is the log from the asterisk server: > > Mar 17 12:01:31 WARNING[2804]: chan_sip.c:6134 receive_info: Unable to parse > INFO message > > > Here is the trace: > > > Frame 96 (808 bytes on wire, 808 bytes captured) > Session Initiation Protocol > Request-Line: INFO sip:6002@192.168.10.90 SIP/2.0 > Method: INFO > Resent Packet: False >...

...;user=phone>;tag=as51ba7d7b Call-ID: 3c325dd38b29-euqotg0g8sr7@snom360 CSeq: 4 INFO Max-Forwards: 70 Contact: <sip:pjf@10.0.1.213:2051;line=t2jii7ty> User-Agent: snom360/3.60r Record: on Content-Length: 0 11 headers, 0 lines Receiving DTMF! Jul 27 17:24:52 WARNING[26025]: chan_sip.c:6166 receive_info: Unable to parse INFO message from 3c325dd38b29-euqotg0g8sr7@snom360. Content Transmitting (no NAT): SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 10.0.1.213:2051;branch=z9hG4bK-q6cqmwneki97 From: "Patrick" <sip:pjf@voip>;tag=1pvw4rlq7s To: <sip:95551212@voip;user=phone&gt...