Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 05-24-2019, 04:51 PM
scarb6 scarb6 is offline
Aspiring Member
 
Join Date: May 2019
Posts: 1
scarb6 has 10 reputation points
Default Phone (SIP) works outgoing, incoming gets busy signal.

I have an Avaya J179 that I just installed. First one on our network. Our other phones are H323 devices except for a few SIP intercoms and conference phones.

We're on Communication Manager 7.1.3 and System Manager 7.1.3.

Long story short, I can make outgoing calls, but incoming calls (external or internal) get a busy signal.

If I log into the same extension on one of our 9608 phones, it works fine.
If I log into the J179 with an extension I know works, now calling that extension will get a busy signal.

I ran a call trace on both a working extension (on a 9608) and the extension on this J179. Working call trace is extension 4601 and the non-working is 4602. (though if I use 4601 on the J179, it won't work)

What step could I have missed? Thanks for any advice!


Working
Code:
                                                                           
16:16:21 TRACE STARTED 05/24/2019 CM Release String cold-01.0.532.0-24811       
16:16:22     G711MU ss:off ps:20                                                
             rgn:1 [10.20.2.11]:50886                                         
             rgn:1 [10.20.1.2]:50054                                          
16:16:24     dial 4061                                                          
16:16:24     term station      4061 cid 0x2c3c                                  
16:16:24     Called party  uses public-unknown-numbering                        

16:16:24 SIP>INVITE sip:4061@kcgc.gov SIP/2.0                                   
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP<SIP/2.0 100 Trying                                                 
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP<INVITE sip:4061@kcgc.gov SIP/2.0                                   
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP>INVITE sip:4061@kcgc.gov SIP/2.0                                   
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP<SIP/2.0 100 Trying                                                 
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP>SIP/2.0 100 Trying                                                 
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP<SIP/2.0 180 Ringing                                                
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP>SIP/2.0 180 Ringing                                                
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP<SIP/2.0 180 Ringing                                                
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           

16:16:24 SIP>PRACK sip:4061@10.102.1.104;gsid=f2e3f262-7e79-41e9-85c            
16:16:24 SIP>e-005056aa1092;epv=%3Csip:4061%40kcgc.gov%3Bgr%3De47298            
16:16:24 SIP>30529cef7cda3536cb4500e1dc%3E SIP/2.0                              
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           
16:16:24     ring station      4061 cid 0x2c3c                                  
16:16:24     Alerting party  uses private-numbering                             

16:16:24 SIP<SIP/2.0 200 OK                                                     
16:16:24     Call-ID: f2e3f79e7e7941e985d105056aa1092                           
             VOIP data from: [10.20.1.2]:50054                                
16:16:33     Jitter:1 0 0 0 0 0 0 0 0 0: Buff:19 WC:12 Avg:1                    
16:16:33     Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0                      
16:16:36     idle station      2554 cid 0x2c3c                                  

16:16:55 TRACE COMPLETE station 2554  cid 0x0
Non-working
Code:
16:02:45 TRACE STARTED 05/24/2019 CM Release String cold-01.0.532.0-24811       
16:02:50     G711MU ss:off ps:20                                                
             rgn:1 [10.20.2.11]:50886                                         
             rgn:1 [10.20.1.2]:50050                                          
16:02:52     dial 4062                                                          
16:02:52     term station      4062 cid 0x2822                                  
16:02:52     Called party  uses public-unknown-numbering                        

16:02:52 SIP>INVITE sip:4062@kcgc.gov SIP/2.0                                   
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092    
                         
16:02:52 SIP<SIP/2.0 100 Trying                                                 
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP<INVITE sip:4062@kcgc.gov SIP/2.0                                   
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP>INVITE sip:4062@kcgc.gov SIP/2.0                                   
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092      

16:02:52 SIP<SIP/2.0 100 Trying                                                 
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP>SIP/2.0 100 Trying                                                 
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP<SIP/2.0 400 Bad Request (Invalid avaya-cm-line)                    
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP>ACK sip:4062@kcgc.gov SIP/2.0                                      
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP>SIP/2.0 400 Bad Request (Invalid avaya-cm-line)                    
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP<SIP/2.0 400 Bad Request (Invalid avaya-cm-line)                    
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52 SIP>ACK sip:4062@kcgc.gov SIP/2.0                                      
16:02:52     Call-ID: f730a07e7841e9824a05056aa1092                             

16:02:52     reorder station      4062 cid 0x2822                               
16:02:56     idle station      2554 cid 

16:03:22 TRACE COMPLETE station 2554  cid 0x0
Reply With Quote
  #2  
Old 08-06-2019, 10:34 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Genius
 
Join Date: Sep 2010
Location: New York
Posts: 396
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

Make sure the J179 is aliased in CM as a 9611SIP. Doublecheck the extension entry in the OPS table also.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:41 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.