Answer the question
In order to leave comments, you need to log in
Why is cisco converting 180 Ringing to 183 Session Progress SDP?
Good afternoon.
There is a scheme
asterisk-----sip----cisco 5400-----h.323----<provider providing 89...>
I am making an outgoing call to 89xxxxxxxxx from the asterisk. Sometimes 180 Ringing comes from the provider to the tsiska, and sometimes 180 Ringing SDP (g711A telephone-event). It seems to depend on the region.
But 183 Session Prigress SDP comes to the asterisk from the tsiska in both cases.
In the case of 180 Ringing SDP, there are no problems, because the voice channel is switched on and the callback is heard from the remote side.
In the case of 180 Ringing on the asterisk, we get 183 Session Prigress SDP and wait for the callback from the remote side and hear silence, although we should send 180 ringing to the sip phone so that it would buzz to us on the phone.
tsiska settings
!
dial-peer voice 50000 voip
tone ringback alert-no-PI
description Out_Leg-to-prov
huntstop
preference 1
destination-pattern 89.
voice-class codec 100
voice-class h323 100
session target ipv4:10.100.0.1
dtmf-relay h245-alphanumeric
fax protocol pass-through g711alaw
ip qos dscp ef signaling
no vad
!
dial-peer voice 40000 voip
tone ringback alert-no-PI
description In_Leg-VOIP
redirect ip2ip
voice-class codec 100
session protocol sipv2
incoming called-number 89.
dtmf-relay rtp-nte
fax rate disable
fax protocol pass-through g711alaw
ip qos dscp ef signaling
no vad
!
Progress inband: Never
Answer the question
In order to leave comments, you need to log in
read Troubleshooting No Ringback Tone on ISDN-VoIP
, although for H.323, but for the most part for SIP, it also applies
a little more here
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question