cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
972
Views
0
Helpful
2
Replies

call forwarded from turret phone, not working.

Abhishek Singh
Cisco Employee
Cisco Employee

We have an issue at one of our locations .

Whenever there is call being forwarded to an outside cell  phone number from turret phone at one of our location  it doesn’t work. (for caller) Call  disconnect after almost 1 minutes of Silence. (For final called pary) his phone  rings for just  second and disconnect and process repeats and lasts about 1  minute.

As per gateway debugs, we  see a setup being  received.

040944: *Dec 15  22:10:53.114 UTC: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x0F4A

Bearer  Capability i = 0x8090A2

Standard  = CCITT

Transfer  Capability = Speech

Transfer  Mode = Circuit

Transfer  Rate = 64 kbit/s

Channel ID i =  0xA98381

Exclusive, Channel 1

Facility i =  0x9F8B0100A10F02013006072A8648CE1500040A0100

Protocol  Profile =  Networking Extensions

0xA10F02013006072A8648CE1500040A0100

Component  = Invoke component

Invoke Id = 48

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Progress Ind i  = 0x8283 - Origination address is non-ISDN

Calling Party  Number i = 0x2183, '214xxxxx51'

Plan:ISDN, Type:National

Called Party  Number i = 0x80, '3052'

Plan:Unknown, Type:Unknown

Then CM sends call setup to turret through another  gateway.

040356: .Dec 15  22:17:05.507 UTC: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8  callref = 0x03AE

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

Facility i =  0x9FAA06800100820100A1080201000201008400

Progress Ind i  = 0x8283 - Origination address is non-ISDN

Calling Party  Number i = 0x2183, '214xxxxx51'

Plan:ISDN, Type:National

Called Party  Number i = 0x80, '3052'

Plan:Unknown, Type:Unknown

Same gatway then receives setup back for the forwarded call  (hairpin)

040947: *Dec 15  22:10:53.718 UTC: ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0694

Sending  Complete

Bearer  Capability i = 0x8090A3

Standard  = CCITT

Transfer  Capability = Speech

Transfer  Mode = Circuit

Transfer  Rate = 64 kbit/s

Channel ID i =  0xA98396

Exclusive, Channel 22

Facility i =  0x9FAA06800100820100A119020209D402011530100201010A0101A108A006800433303532

Calling Party  Number i = 0x0083, '21xxxxxx51'

Plan:Unknown, Type:Unknown

Called Party  Number i = 0x80, '91.......388'

Plan:Unknown, Type:Unknown

Call manager  then forwards the call to telco

040949: *Dec 15  22:10:53.838 UTC: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8  callref = 0x050F

Bearer  Capability i = 0x8090A2

Standard  = CCITT

Transfer  Capability = Speech

Transfer  Mode = Circuit

Transfer  Rate = 64 kbit/s

Channel ID i =  0xA98397

Exclusive, Channel 23

Calling Party  Number i = 0x2183, '21......51'

Plan:ISDN, Type:National

Called Party  Number i = 0xA1, '171........88'

Plan:ISDN, Type:National

040950: *Dec 15  22:10:53.902 UTC: ISDN Se0/0/1:23 Q931: RX <- CALL_PROC pd = 8  callref =  0x850F

For which we  receive a progress ind from telco.

040951: *Dec 15  22:10:56.478 UTC: ISDN Se0/0/1:23 Q931: RX <- PROGRESS pd = 8  callref =  0x850F

Progress Ind i  = 0x8288 - In-band info or appropriate now available

We receive no  message for next 10 seconds.

After 10  seconds the call originating telco disconnects the call.

040953: *Dec 15  22:11:03.306 UTC: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref =  0x0F4A

Cause i =  0x80E6 - Recovery on timer expiry

collected traces for successful call hoever in that call telco doesn’t send call  proc in response to set. It  sends alerting.

In both good  and bad call case call is going out through same circuit. That is 0/0/1  of srst  gateway of the location.

Can somebody guide on this.

Whatever level you reach getting better never stops -- Sachin Tendulkar
2 Replies 2

Mike Lydick
Level 1
Level 1

Are these H323 dialpeers. Have you adjusted the H225 call setup timers? Also have you adjusted callmanager to allow for additional call connect time? Seems from the call you are transverse a few gateways and the call connect is timing out.

The T310 Timer sets how long to wait to get a response such as ALERTING or CONNECT to  a Call Proceeding message.

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094487.shtml

Cause i =  0x80E6 indicates timeout on a longdistance call. Looks like the carrier is looking for a connect mesg and does not recieve so it times out.

Mike

carrier sends a calls progressing note.. can attach the deubgs if u want.

Whatever level you reach getting better never stops -- Sachin Tendulkar
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: