06-06-2005 10:48 PM - edited 03-13-2019 09:22 AM
Hello Team,
CM 4.1(2)sr2
3845 - 12.3(14)T2 (H323)
Commander PBX
E1 PRI connection between Commander and 3845.
Guys whenever we dial certain numbers in the US these are hospital numbers we receive no alerting Ringback either on the IP phone or PBX phone.
Here is a snip of the q931 debugs from PRI. And attached is the debug isdn q931 and debug voip ccapi inout.
Jun 5 23:59:05.774: ISDN Se3/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x3436
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Progress Ind i = 0x8183 - Origination address is non-ISDN
Called Party Number i = 0x80, '001118145343374'
Plan:Unknown, Type:Unknown
Jun 5 23:59:05.954: ISDN Se3/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0xB436
Channel ID i = 0xA9839F
Exclusive, Channel 31
Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
I added the usuall Progress_ind alert enable 8, Progress_ind setup enable 3, tone ringback alert-no-pi under the POTS dial peers voice call send-recv as well as voice call send-alert, but the problem still presists.
This is currently affecting our users and wish to have it fixed for them.
If i call from any other phone system or mobile i receive/hear ringback and prior to our integration between TDM and IP Tel environment problem has become evident.
I have this feeling that the other end is NON ISDN and is not sending a progress ind PI =8 or PI =3 while in alerting stage of ISDN call. Is there any other way to force on our router to send an alerting to phones or or way to get around this issue.
Thank you,
Yavuz
Network and Communication Engineer
Nighthawk Radiology Services
06-07-2005 10:01 PM
Hey Yabuz
Try adding "isdn incoming alerting add-PI" on the
ISDN serial interface for D channel.
Let us know if that helps.
06-07-2005 10:38 PM
Hi,
as it looks from the debug, the destination PSTN switch does not send ALERTING at all. It sends CALL PROCEEDING instead.
The "alert-no-pi" command shall not work, as you ar not getting an ALERTING message at ALL.
You hvae to keep the voice rtp send-recv command, as you *do not get any PI* in the CALL PROCEEDING message. However the command is "voice rtp send-recv", be sure that it is entered correctly.
You have to add the alert_ind at the "terminating" dialpeer.
Let me know if it helps, if not I have another idea (but you have to show me your dialpeers) and if still "not" - sorry :(
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide