CUCM - Cube - Verizon sip call disconnect after two rings

[duane basterash]

I have a user that is trying to call one of their members. The call rings twice on users end and then call just hangs up. I will attach the debug ccsip messages but here is my interpretation:

CUCM                    Cube                    Verizon

invite-->

                                   Invite--->

               <-----Trying

                                            <------Trying

                                             <------183 Session Progress

               <-----183 Session Progress

                                             <----487 Request Terminated

                                   ACK--->

               <------500 internal Server Error

Ack----->>>>

I have difficulty reading to and from on SIP debug so this could be wrong and i need my thought process verified.

Not sure if it matters but there is an almost 9 second gap between session progress and 487 request terminated.

Called number 8-838-5958

Calling number 2622922500

10.10.10.21 Cube

192.168.10.6 CUCM 8.6

[Ayodeji Okanlawon]

Duane,

I work for Verizon and we use broadworks/broad sosft for most of our customers...Most times when you get 487 from broad soft, its usually because the CLI you have presented is not correct..Is this DDI correct or part of your block (2622922500)..

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[duane basterash]

aokanlawon,

Yes the 2622922500 is part of the block. I have tested with other numbers and have been successful calling other numbers. The user reports this happening to other numbers but i do not have other examples and cannot verify.

Did you happen to look at the debug and can you verify my logic?

Thank you for your response.

[Ayodeji Okanlawon]

I did look at the debug and in my experience especially with broadsoft 99% of the time when you dial out, you get a long silence and the call disconnects, its due to rong CLI. If you are sure that the CLI is correct, then you need to open a ticket with the broad sfot guys and have them investigate it because they are the one terminating the request

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[Dennis Mink]

Raised it with MCI Worldcom  Verizon the as the debug clearly shows that they are initiating the request terminated  (and you are right there is a 7 second gap between the last session progress and the  487.

Little tip on looking at SIP traces; use notepad ++ and use the Call ID as a search criterium, very handy when looking at a gateway with lots of various calls.

Nov 13 08:30:37.997: //1794353/23A8B6000001/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 487 Request terminated

Via: SIP/2.0/UDP 10.10.10.21:5060;branch=z9hG4bK29F312E08

From: "MequonTest" <2622922500>;tag=6EDDEE6E-2269

To: <8385958>;tag=91152707-1384353030025

Call-ID: FAEC5303-4BA611E3-82EEF1D9-62A5C848@10.10.10.21

=============================
Please remember to rate useful posts, by clicking on the stars below. 

=============================