Email Subscription Notifications Suspended Temporarily
We are in the process of making navigation in the Servers and Operating Systems forums simpler and more direct. While doing this, we have to temporarily suspend email notifications for subscriptions. If you are subscribed to one or more discussion boards or blogs in the community, please check them daily to see new content. Notifications will be turned back on in a few days. We apologize for any inconvenience this may cause. Thanks, Warren_Admin
IP Telephony - NBX
cancel
Showing results for 
Search instead for 
Did you mean: 

No Ring for Incoming Callers

xaositects
Advisor

No Ring for Incoming Callers

Background Info:



incoming line is an ISDN/PRI hooked up through a gateway chassis with a T1 Line card.



NBX is a V3001 (3CR10800A)



We just moved to a new provider but the settings should all have been the same.



 



Problem:



When dialing in to any DID, the incoming caller does not hear a ring, they only hear silence, but the receiving phone rings fine. Obviously this results in many people hanging up before the phone is answered because it sounds like the phone is dead.



 



Any ideas? telco says they see the line sending an alert signal for the ring, but the NBX isn't sending it back.

15 REPLIES
merlin_1
Super Advisor

Re: No Ring for Incoming Callers

The CO provides ringback .  Discuss this with your carrier and they should be able to " play ringback " on the call .



What version of code ?  I heard something like this a few years ago , and again it was a Telco issue .



xaositects
Advisor

Re: No Ring for Incoming Callers

NBX is running R6_5_22



I updated the ticket I've got in with TW Telecom. Will post back here if no resolution.

xaositects
Advisor

Re: No Ring for Incoming Callers

This is the reply from the technician:



"THE FAR END EQUIPMENT ALWAYS PROVIDES RING BACK - IF THE NUMBER IS A LINE IN THE SWITCH THEN THE CO IS THE FAR END EQUIPMENT AND SENDS THE RING BACK . IN THIS SITUATION THAT IS HAPPENING - YOUR EQUIPMENT IS SENDING THE RING BACK IN AN 'ALERTING' MESSAGE.





THE PROBLEM IS THAT YOUR EQUIPMENT IS NOT SENDING A CALL PROGRESS MESSAGE OR A CALL PROCEEDING MESSAGE WITH AN INDICATOR TO THE NETWORK TO OPEN THE 'B' CHANNEL SO THE OTHER END CAN HEAR THE RING BACK.  YOU CAN SEND THIS IN THE ALERTING OR IN A SEPARATE PROCEEDING OR PROGRESS MESSAGE.  IT HAS TO SHOW EITHER 'INBAND INFORMATION IS AVAILABLE' OR ' CALL IS NOT END TO END ISDN' AND THE NETWORK WILL OPEN THE 'B' CHANNEL AND THE ORIGINATING SIDE CAN HEAR YOUR RING .  I WILL SEND YOU A TRAP IN ANOTHER EMAIL."



 



Not sure why it's different with this telco. WOrked fine with the last.



 



Edit:



Here's the Q931 ------------->








Aug 27 14:41:42.265: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0992


        Bearer Capability i = 0x8090A2


                Standard = CCITT


                Transfer Capability = Speech  


                Transfer Mode = Circuit


                Transfer Rate = 64 kbit/s


        Channel ID i = 0xA98383


                Exclusive, Channel 3


        Facility i = 0x9F8B0100A113020138020100800B556E617661696C61626C65


                Protocol Profile =  Networking Extensions


                0xA113020138020100800B556E617661696C61626C65


                Component = Invoke component


                        Invoke Id = 56


                        Operation = CallingName


                                Name Presentation Allowed Extended


                                Name = Unavailable


        Display i = 'Unavailable'


        Calling Party Number i = 0x2180, 'Restricted'


                Plan:ISDN, Type:National


        Called Party Number i = 0x80, '1743'


                Plan:Unknown, Type:Unknown


Aug 27 14:41:42.309: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8  callref = 0x8992


        Channel ID i = 0xA98383


                Exclusive, Channel 3


Aug 27 14:41:42.313: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x8992


        Cause i = 0x8091 - User busy


Aug 27 14:41:42.317: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x0992


Aug 27 14:41:42.341: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8992



This message was edited by xaositects on 8-27-10 @ 1:16 PM
merlin_1
Super Advisor

Re: No Ring for Incoming Callers

Not exactly sure what he means by this statement



"THE FAR END EQUIPMENT ALWAYS PROVIDES RING BACK - IF THE NUMBER IS A  LINE IN THE SWITCH THEN THE CO IS THE FAR END EQUIPMENT AND SENDS THE  RING BACK . IN THIS SITUATION THAT IS HAPPENING - YOUR EQUIPMENT IS  SENDING THE RING BACK IN AN 'ALERTING' MESSAGE.


 



I am verifying the statement I made about them supplying ring back . I may be wrong but I have questions about the above statement as well



 



As far as below , if the statement above is true , then this would occur because  I would assume its a different set up to us .












THE PROBLEM IS  THAT YOUR EQUIPMENT IS NOT SENDING A CALL PROGRESS MESSAGE OR A CALL  PROCEEDING MESSAGE WITH AN INDICATOR TO THE NETWORK TO OPEN THE 'B'  CHANNEL SO THE OTHER END CAN HEAR THE RING BACK.  YOU CAN SEND THIS IN  THE ALERTING OR IN A SEPARATE PROCEEDING OR PROGRESS MESSAGE.  IT HAS TO  SHOW EITHER 'INBAND INFORMATION IS AVAILABLE' OR ' CALL IS NOT END TO  END ISDN' AND THE NETWORK WILL OPEN THE 'B' CHANNEL AND THE ORIGINATING  SIDE CAN HEAR YOUR RING .  I WILL SEND YOU A TRAP IN ANOTHER EMAIL."



 



I'll find out and repost .....



Stand By ....



 



xaositects
Advisor

Re: No Ring for Incoming Callers

Basically, the line card is sending the ring, but not opening the b channel. Is there a way to set that while logged into the line card via hyperteminal? I can't ifnd any docs on it, aside from setting the line card to output debug messages



merlin_1
Super Advisor

Re: No Ring for Incoming Callers

Unfortunately there is no way to change those settings . I  am totally mistyfied as to why the carrier is requiring this as I am still searching for some info ....



Turn on PRI logging on the card. Connect a console port to the PRI card.


At the -> prompt, type nbxSetMsgTypeFilter "DSPMGR", -1


 Next type, cli, then


  stklog -iep on -ier on -ieh on -dlr on -ilr on



to shut off ;



stklog -iep off -ier off -ieh off -dlr off -ilr off



 



 



This message was edited by merlin on 9-1-10 @ 12:13 PM
xaositects
Advisor

Re: No Ring for Incoming Callers

Yeah I've set that before to track down a bouncing span we had before but in this case, I'm not sure what I'm looking for in the log.



 



And, I can't figure out why they require that either.



xaositects
Advisor

Re: No Ring for Incoming Callers

I get this from the log when calling in.



 



0902:115910 ADC            I NT: SETUP_IND            Chan: 0x03, CallID 0x02f1


0902:115910 ADC            I     BearerCaps    (0x04) TxC: 0x00 TxR 0x10


0902:115910 ADC            I         Cdg: 0x02 URt: 0x0b


0902:115910 ADC            I     ChannelID     (0x18) Chn: 0x03 P/E: EXCL


0902:115910 ADC            I     CallingNumber (0x6c) ToN: NAT Pln: ISDN


0902:115910 ADC            I         Num: __REMOVED__ Prs: ALLOW Scr: U-PROV


0902:115910 ADC            I     CalledNumber  (0x70) ToN: UNK Pln: UNK


0902:115910 ADC            I         Num: 1715


0902:115910 ADC            I     Facility (0x1C)


0902:115910 ADC            I     Raw IE Data


0902:115911 ADC            I         00 04 0a 80 80 80 90 00 00 00 00 00 82 00 18 0b


0902:115911 ADC            I         81 81 80 81 00 00 80 03 00 00 04 00 1c 19 9f 81


0902:115911 ADC            I         8b 01 00 a1 12 02 01 57 02 01 00 80 0a 4d 49 4c


0902:115911 ADC            I         4c 45 52 2c 54 4f 4d 00 6c 0e 82 81 80 80 34 30


0902:115911 ADC            I         37 36 38 33 32 35 37 34 00 70 06 80 80 31 37 31


0902:115911 ADC            I         35


0902:115911 ADC            I TE: ALERT_REQ            Chan: 0x03, CallID 0x02f1


0902:115911 ADC            I     ChannelID     (0x18) Chn: 0x03 P/E: EXCL


0902:115911 ADC            I     Raw IE Data


0902:115911 ADC            I         00 18 0b 81 81 80 81 00 00 80 03 00 00 04


0902:115911 ADC            I TE:    00 01 de ee 08 02 8f 99 01 18 03 a9 83 83


0902:115911 ADC            I NT:    00 01 01 e0


0902:115920 DSPMGR         E **** HPICmdToneDetFcnT Chan -1 ****


0902:115920 DSPMGR         E (1) SlaveCommand 0x1006 - ToneActivate 0x1


0902:115920 DSPMGR         E (1) ToneType 0x0


0902:115920 DSPMGR         E **** NIPTEPAudioConnDataT Chan -1 ****


0902:115920 DSPMGR         E (1) TempIPMask 0.0.0.0


0902:115920 DSPMGR         E (1) CallProgToneModeVol 0x0 - CallProgDuration 0x0


0902:115920 DSPMGR         E **** NIPTEPCallProcessBlockT Chan -1 ****


0902:115920 DSPMGR         E (1) ConnectionTypeDir 0x3 - AudioHeaderBits 0x9


0902:115920 DSPMGR         E (1) AudioIPTOS 0x0000 - AudioTagControl 0x0000


0902:115920 DSPMGR         E (1) CompressionVolumeInfo 0x0300


0902:115921 DSPMGR         E (1) AudioControlandFramesNo 0x5 - TerminationSeqMask 0x0


0902:115921 DSPMGR         E (1) tOtherParty.PartyMAC e0:bb39:3d25 - tOtherPartyVDN 0x101


0902:115921 DSPMGR         E (1) OtehrPartyIP 0.0.0.0


0902:115921 DSPMGR         E (1) GatewayIP 0.0.0.0


0902:115921 DSPMGR         E (1) MultiCastMACToListen 0:0:0


0902:115921 DSPMGR         E (1) MultiCastHashCode 0xff


0902:115921 DSPMGR         E (1) MulitCastIP 0.0.0.0


0902:115921 DSPMGR         E **** NIPConferenceControlBlockT Chan -1: No participants ****


0902:115921 ADC            I TE: CONNECT_REQ          Chan: 0x01, CallID 0x02f0


0902:115921 ADC            I     No Raw IE Data


0902:115921 ADC            I TE:    00 01 e0 ee 08 02 8f 98 07


0902:115921 ADC            I NT:    00 01 01 e2


0902:115921 ADC            I NT:    02 01 ee e2 08 02 0f 98 0f


0902:115921 ADC            I TE:    02 01 01 f0


0902:115921 ADC            I NT: CONNECT_CONF         Chan: 0x01, CallID 0x02f0


0902:115922 ADC            I     No Raw IE Data


0902:115922 DSPMGR         E **** HPICmdToneDetFcnT Chan -1 ****


0902:115922 DSPMGR         E (1) SlaveCommand 0x1006 - ToneActivate 0x1


0902:115922 DSPMGR         E (1) ToneType 0x0


0902:115922 DSPMGR         E **** HPICmdCallProgFcnT Chan -1 ****


0902:115922 DSPMGR         E (1) SlaveCommand 0x1005 - CallProgDetActivate 0x1


0902:115922 DSPMGR         E (1) CallProgToneModeVol 0xff00 - CallProgDetDuration 0x0


0902:115922 DSPMGR         E **** NIPTEPAudioConnDataT Chan -1 ****


0902:115922 DSPMGR         E (1) TempIPMask 0.0.0.0


0902:115922 DSPMGR         E (1) CallProgToneModeVol 0x0 - CallProgDuration 0x0


0902:115922 DSPMGR         E **** NIPTEPCallProcessBlockT Chan -1 ****


0902:115922 DSPMGR         E (1) ConnectionTypeDir 0x202 - AudioHeaderBits 0x9


0902:115922 DSPMGR         E (1) AudioIPTOS 0x0000 - AudioTagControl 0x0000


0902:115922 DSPMGR         E (1) CompressionVolumeInfo 0x0300


0902:115923 DSPMGR         E (1) AudioControlandFramesNo 0x5 - TerminationSeqMask 0xffff


0902:115923 DSPMGR         E (1) tOtherParty.PartyMAC e0:bb39:3d25 - tOtherPartyVDN 0x101


0902:115923 DSPMGR         E (1) OtehrPartyIP 0.0.0.0


0902:115923 DSPMGR         E (1) GatewayIP 0.0.0.0


0902:115923 DSPMGR         E (1) MultiCastMACToListen 0:0:0


0902:115923 DSPMGR         E (1) MultiCastHashCode 0xff


0902:115923 DSPMGR         E (1) MulitCastIP 0.0.0.0


0902:115923 DSPMGR         E **** NIPConferenceControlBlockT Chan -1: No participants ****


0902:115925 ADC            I NT:    02 01 f0 e2 08 02 0f 99 45 08 02 82 90


0902:115925 ADC            I TE:    02 01 01 f2


0902:115925 ADC            I NT: DISCONNECT_IND       Chan: 0x03, CallID 0x02f1


0902:115925 ADC            I     Cause         (0x08) Loc: 0x00


0902:115925 ADC            I         Cse: 0x10 NORMAL_CLEARING



This message was edited by xaositects on 9-2-10 @ 11:02 AM
xaositects
Advisor

Re: No Ring for Incoming Callers

is there a newer version of this card available that might fix this problem?



merlin_1
Super Advisor

Re: No Ring for Incoming Callers

You should really open a case up with our tech support .



There is no new cards as the D card is the last board built and software has no fix for this . Our tech support can be of more help . In the alerting message is the ring back , If the CO , was waiting for this we would send a message stating to play ring back . If we were to play ring back , then we would recive a message in the alert to play ring back . I am pretty sure we supply ring back  but I cannot verify yet .



Between the Alerting and the Connect is appriox . 10 seconds , 2 rings . I am not sure if the ringback message is in there .



0902:115911 ADC            I TE: ALERT_REQ            Chan: 0x03, CallID 0x02f1





0902:115911 ADC            I     ChannelID     (0x18) Chn: 0x03 P/E: EXCL





0902:115911 ADC            I     Raw IE Data





0902:115911 ADC            I         00 18 0b 81 81 80 81 00 00 80 03 00 00 04





0902:115911 ADC            I TE:    00 01 de ee 08 02 8f 99 01 18 03 a9 83 83





0902:115911 ADC            I NT:    00 01 01 e0





0902:115920 DSPMGR         E **** HPICmdToneDetFcnT Chan -1 ****





0902:115920 DSPMGR         E (1) SlaveCommand 0x1006 - ToneActivate 0x1





0902:115920 DSPMGR         E (1) ToneType 0x0





0902:115920 DSPMGR         E **** NIPTEPAudioConnDataT Chan -1 ****





0902:115920 DSPMGR         E (1) TempIPMask 0.0.0.0





0902:115920 DSPMGR         E (1) CallProgToneModeVol 0x0 - CallProgDuration 0x0





0902:115920 DSPMGR         E **** NIPTEPCallProcessBlockT Chan -1 ****





0902:115920 DSPMGR         E (1) ConnectionTypeDir 0x3 - AudioHeaderBits 0x9





0902:115920 DSPMGR         E (1) AudioIPTOS 0x0000 - AudioTagControl 0x0000





0902:115920 DSPMGR         E (1) CompressionVolumeInfo 0x0300





0902:115921 DSPMGR         E (1) AudioControlandFramesNo 0x5 - TerminationSeqMask 0x0





0902:115921 DSPMGR         E (1) tOtherParty.PartyMAC e0:bb39:3d25 - tOtherPartyVDN 0x101





0902:115921 DSPMGR         E (1) OtehrPartyIP 0.0.0.0





0902:115921 DSPMGR         E (1) GatewayIP 0.0.0.0





0902:115921 DSPMGR         E (1) MultiCastMACToListen 0:0:0





0902:115921 DSPMGR         E (1) MultiCastHashCode 0xff





0902:115921 DSPMGR         E (1) MulitCastIP 0.0.0.0





0902:115921 DSPMGR         E **** NIPConferenceControlBlockT Chan -1: No participants ****





0902:115921 ADC            I TE: CONNECT_REQ          Chan: 0x01, CallID 0x02f0


 



 



This message was edited by merlin on 9-9-10 @ 7:13 AM
xaositects
Advisor

Re: No Ring for Incoming Callers

Yeah I sent a message to 3com tech support yesterday. I'm awaiting their reply now. Thanks for your help.



xaositects
Advisor

Re: No Ring for Incoming Callers

I've been searchign around to find another option but can't seem to find one. Is there another card for the nbx gateway chassis that will connect to a PRI?



merlin_1
Super Advisor

Re: No Ring for Incoming Callers

No latest rev is a D board .



xaositects
Advisor

Re: No Ring for Incoming Callers

yeah apparently I need to switch to a VCX system to solve this problem.



xaositects
Advisor

Re: No Ring for Incoming Callers

well, this problem is solved. Turned out to be the telco's problem.