Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

Outbound calls just Ring

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


lemon at lemon

Feb 28, 2008, 7:49 AM

Post #1 of 3 (1110 views)
Permalink
Outbound calls just Ring

Hi,

Have CCM 6.0 running with 6 PRI's split over two AS5350XM's. When
dialing out we sometimes get that it just rings and rings and rings.
If you phone the same number from a mobile phone you get an immediate
response. Below some debug output:




Feb 28 15:39:34.824: ISDN Se3/1:15 Q931: TX -> SETUP pd = 8 callref = 0x1C05
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98392
Exclusive, Channel 18
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0181, '8021'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '1850602602'
Plan:Unknown, Type:Unknown
Feb 28 15:39:34.972: ISDN Se3/1:15 Q931: RX <- CALL_PROC pd = 8
callref = 0x9C05
Channel ID i = 0xA98392
Exclusive, Channel 18
Feb 28 15:39:35.068: ISDN Se3/1:15 Q931: RX <- ALERTING pd = 8
callref = 0x9C05
Progress Ind i = 0x8482 - Destination address is non-ISDN
Progress Ind i = 0x8488 - In-band info or appropriate now available

Thnx
_______________________________________________
cisco-voip mailing list
cisco-voip[at]puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


ninergoose at yahoo

Feb 28, 2008, 11:40 AM

Post #2 of 3 (1083 views)
Permalink
Re: Outbound calls just Ring [In reply to]

Is it always the same number called? Or a different (random) number? We had a somewhat similar situation but the calls were random (at least they seemed random) across 8 PRIs. One individual PRI had an issue on the telco side. The Route Group was set to circular, so one out of every 8 outbound calls would have an issue because it hit the bad PRI. The system was large enough that no one recognized it was every 8th call. We "lucked" into finding it by setting the RG to top down. Once we did that, the call volume wasn't large enough to spill into that PRI so all calls worked. We then started testing them individually.

Also, I personally would set the calling type to National, but I don't believe that has anything to do with your issue.

-Go0se


Lemon <lemon[at]lemon.za.net> wrote:
Hi,

Have CCM 6.0 running with 6 PRI's split over two AS5350XM's. When
dialing out we sometimes get that it just rings and rings and rings.
If you phone the same number from a mobile phone you get an immediate
response. Below some debug output:




Feb 28 15:39:34.824: ISDN Se3/1:15 Q931: TX -> SETUP pd = 8 callref = 0x1C05
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98392
Exclusive, Channel 18
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0181, '8021'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '1850602602'
Plan:Unknown, Type:Unknown
Feb 28 15:39:34.972: ISDN Se3/1:15 Q931: RX <- CALL_PROC pd = 8
callref = 0x9C05
Channel ID i = 0xA98392
Exclusive, Channel 18
Feb 28 15:39:35.068: ISDN Se3/1:15 Q931: RX <- ALERTING pd = 8
callref = 0x9C05
Progress Ind i = 0x8482 - Destination address is non-ISDN
Progress Ind i = 0x8488 - In-band info or appropriate now available

Thnx
_______________________________________________
cisco-voip mailing list
cisco-voip[at]puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



---------------------------------
Never miss a thing. Make Yahoo your homepage.


lemon at lemon

Mar 2, 2008, 11:52 AM

Post #3 of 3 (1060 views)
Permalink
Re: Outbound calls just Ring [In reply to]

Hi,



On Thu, Feb 28, 2008 at 7:40 PM, Scot Gossen <ninergoose[at]yahoo.com> wrote:
> Is it always the same number called? Or a different (random) number? We had
> a somewhat similar situation but the calls were random (at least they seemed
> random) across 8 PRIs. One individual PRI had an issue on the telco side.
> The Route Group was set to circular, so one out of every 8 outbound calls
> would have an issue because it hit the bad PRI. The system was large enough
> that no one recognized it was every 8th call. We "lucked" into finding it by
> setting the RG to top down. Once we did that, the call volume wasn't large
> enough to spill into that PRI so all calls worked. We then started testing
> them individually.

It is kinda random yes. After running some more debugs, we noticed
that the Voice gateway is getting a disconnect from the provider and
then tried reconnecting the call. So if the user does not hang up,
after about 60 seconds, the call eventually starts ringing on the
other side.

IPTvg2B#
Feb 29 19:56:54.184: ISDN Se3/2:15 Q931: Applying typeplan for sw-type 0x12 is 0
x0 0x1, Calling num 4004
Feb 29 19:56:54.184: ISDN Se3/2:15 Q931: Applying typeplan for sw-type 0x12 is 0
x0 0x0, Called num 0876695247
Feb 29 19:56:54.184: ISDN Se3/2:15 Q931: TX -> SETUP pd = 8 callref = 0x0CF0
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
Calling Party Number i = 0x0181, '4004'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '0876695247'
Plan:Unknown, Type:Unknown
Feb 29 19:56:54.388: ISDN Se3/2:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8CF
0
Channel ID i = 0xA9839F
Exclusive, Channel 31
Feb 29 19:56:54.552: ISDN Se3/2:15 Q931: RX <- PROGRESS pd = 8 callref = 0x8CF0

Progress Ind i = 0x8482 - Destination address is non-ISDN
Progress Ind i = 0x8288 - In-band info or appropriate now available
Feb 29 19:57:20.144: ISDN Se3/2:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8C
F0
Cause i = 0x05809F - Normal, unspecified
Progress Ind i = 0x8288 - In-band info or appropriate now available
Feb 29 19:57:20.144: ISDN Se3/2:15 Q931: call_disc: PI received in disconnect; P
ostpone sending RELEASE for callid 0x8C79
Feb 29 19:57:50.992: ISDN Se3/2:15 Q931: RX <- RELEASE pd = 8 callref = 0x8CF0
Cause i = 0x05809F - Normal, unspecified
Cause i = 0x0280E6333036 - Recovery on timer expiry
Feb 29 19:57:50.992: ISDN Se3/2:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x
0CF0
Feb 29 19:57:50.996: ISDN Se3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0
x0 0x1, Calling num 4004
Feb 29 19:57:50.996: ISDN Se3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0
x0 0x0, Called num 0876695247
Feb 29 19:57:50.996: ISDN Se3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0CF1
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
Calling Party Number i = 0x0181, '4004'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '0876695247'
Plan:Unknown, Type:Unknown
Feb 29 19:57:51.132: ISDN Se3/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8CF
1
Channel ID i = 0xA9839F
Exclusive, Channel 31
Feb 29 19:57:56.524: ISDN Se3/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8CF1

Progress Ind i = 0x8488 - In-band info or appropriate now available
Feb 29 19:57:59.832: ISDN Se3/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0C
F1
Cause i = 0x8090 - Normal call clearing
Feb 29 19:57:59.892: ISDN Se3/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8CF1
Feb 29 19:57:59.892: ISDN Se3/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x
0CF1
_______________________________________________
cisco-voip mailing list
cisco-voip[at]puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.