Resending to include Matt

-------------------------------------------------------------------------------From: Mai Gregory Sent: Tuesday, April 15, 2008 4:26 AM To: 'davide budicin'; 'Walter Papili'; 'Pratik Kapadia' Cc: 'Van-orden, Jon'; 'Antonio Coricciati'; 'Luisa Pianta'; Jeff Allen; Pinakin Patel; ChristopherW White Subject: RE: MTM call failure

Davide,

Could you please perform the following commands? telnet 172.16.245.74. Connected to 172.16.245.74.. Escape character is '^]'. Telnet session Welcome to CMM Telnet Shell Login: root Password: root N01-M107-0701.40.1D-Telnet>

Logging into the PAC 7 CPU 0

N01-M107-0701.40.1D-Telnet> send 7,0:connect N01-M107-0701.40.1D-C> N01-M107-0701.40.1D-C> trct 1 720 N01-M107-0701.40.1D-C> cmi cfg 3 0 N01-M107-0701.40.1D-C> cmi cfg 1 0

Thanks, Mai

-------------------------------------------------------------------------------From: Mai Gregory Sent: Monday, April 14, 2008 5:39 PM To: 'davide budicin'; Walter Papili; Pratik Kapadia Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; Jeff Allen; Pinakin Patel; ChristopherW White Subject: RE: MTM call failure

All,

After reviewing the ethereal trace, provided by Davide and Walter, and discussio n with Pratik from Kineto, we have come to a conclusion that the cable connected from GiGe port 1 in slot 19 is not connected directly to the LBR. The ARP from MGW in the ethereal cs call issue 14_04 a.pcap shows that it is sent to Cisco_2b: f3:00 which is the Cisco 2950.

Attach is the diagram of the network configuration. You can see that the dark y ellow line connect the GiGe port 1 to the LBR (172.16.245.49). Can we confirm the cable connection and capture ethereal trace?

Thanks, Mai G

-------------------------------------------------------------------------------From: davide budicin [mailto:davide.budicin@EU.NEC.COM] Sent: Monday, April 14, 2008 8:35 AM To: Mai Gregory; Walter Papili; Pratik Kapadia Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; Jeff Allen; Pinakin Patel Subject: R: MTM call failure

Mai,

please find attached logs reporting an MOC and an MTM. There are two wireshark logs, both reporting an MOC and an MTM, we got the first when tracing CPU0 and the second one when tracing CPU1.

Thanks and regards, Davide Budicin Systems and Infrastructures Division NEC Italia S.R.L Mobile: +39 335 1335735 Office: +39 02 48415354 ========================================================== This message and any attachments are intended for the use of the addressee and m ay contain information that is confidential and privileged or otherwise protecte d from disclosure. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is not authorised. If you are not the in tended recipient, please immediately notify the sender and delete this message a nd the attachment from your system. Opinions, conclusions and other information contained in this message that do not relate to the official business of NEC Ita lia Srl, its parents or subsidiaries, shall not be understood as endorsed by NEC Italia Srl, its parent or subsidiaries and no liability will be accepted for th e same. Any legally binding agreement resulting from its contents must be made s eparately in a printed medium. -------------------------------------------------------------------------------Da: Mai Gregory [mailto:Mai.Gregory@genband.com] Inviato: venerd 11 aprile 2008 23.46 A: davide budicin; Walter Papili; Pratik Kapadia Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; Jeff Allen; Pinakin Patel Oggetto: RE: MTM call failure

Davide,

After reviewing the log provided, I do not see a MTM call being requested from I NC. Can you please turn on the trace again and capture ethereal and log for a MTM ca ll?

Walter, my Skype id is mai_gregory.

Thanks, Mai

telnet 172.16.245.74. Connected to 172.16.245.74.. Escape character is '^]'. Telnet session Welcome to CMM Telnet Shell Login: root Password: root N01-M107-0701.40.1D-Telnet>

Logging into the PAC 7 CPU 0

N01-M107-0701.40.1D-Telnet> send 7,0:connect N01-M107-0701.40.1D-C> N01-M107-0701.40.1D-C> trct 1 720 change auto time trace restore switch to 1 change auto time trace restore time interval to 720

N01-M107-0701.40.1D-C> trce 7 1 CRM L5 slot 7 cpu 1 app CRM trace level = L1 L2 L3 L4 L5 L6 L7 L8 Do you want to change CRM trace level of the slot 7 cpu 1 to L1 -- L5 ? (Y/N) y TrcEnable Done !

Starting MEGACO and ALCAP traces on PAC 7 CPU 0

N01-M107-0701.40.1D-C> N01-M107-0701.40.1D-C> meg 0 0

Subsystem values: gen=0 sm=1 mib=2 sck=3 cfg=4 Enter subsystem: 3 Filter level values: =0 =1 =2 =3 =4 Enter new level: 0 N01-M107-0701.40.1D-C> trce 7 0 ALCAP L3

Starting CRM traces on PAC 7 CPU 1

N01-M107-0701.40.1D-Telnet> send 7,1:connect N01-M207-0701.40.1A-C>

N01-M207-0701.40.1A-C> msgt sccp egcp alcap

Are you sure you want to modify message trace? [y/n] : y Msg trace on primitive type : EGCP+SCCP+ALCAP Trace mode : Text **** To activate message trace, enable CRM level 3 trace on CPU 0

-------------------------------------------------------------------------------From: davide budicin [mailto:davide.budicin@EU.NEC.COM] Sent: Friday, April 11, 2008 7:51 AM To: Mai Gregory; Walter Papili; Pratik Kapadia Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; Jeff Allen; Pinakin Patel Subject: R: MTM call failure

Mai,

I m sorry, in my previous mail I forgot to attach the PAC7-CPU1 log.

Thanks, Davide Budicin

Systems and Infrastructures Division NEC Italia S.R.L Mobile: +39 335 1335735 Office: +39 02 48415354 ========================================================== This message and any attachments are intended for the use of the addressee and m ay contain information that is confidential and privileged or otherwise protecte d from disclosure. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is not authorised. If you are not the in tended recipient, please immediately notify the sender and delete this message a nd the attachment from your system. Opinions, conclusions and other information contained in this message that do not relate to the official business of NEC Ita lia Srl, its parents or subsidiaries, shall not be understood as endorsed by NEC Italia Srl, its parent or subsidiaries and no liability will be accepted for th e same. Any legally binding agreement resulting from its contents must be made s eparately in a printed medium. -------------------------------------------------------------------------------Da: Mai Gregory [mailto:Mai.Gregory@genband.com] Inviato: venerd 11 aprile 2008 0.28 A: Walter Papili; Pratik Kapadia Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; davide budicin; Jeff Allen ; Pinakin Patel Oggetto: RE: MTM call failure

Walter,

Can you check to see if the adjacent node ALCAP is enabled? If it is enabled, p lease perform the following and capture ethereal and log.

telnet 172.16.245.74. Connected to 172.16.245.74.. Escape character is '^]'. Telnet session Welcome to CMM Telnet Shell Login: root Password: root N01-M107-0701.40.1D-Telnet>

Logging into the PAC 7 CPU 0

N01-M107-0701.40.1D-Telnet> send 7,0:connect N01-M107-0701.40.1D-C> N01-M107-0701.40.1D-C> trct 1 720 change auto time trace restore switch to 1 change auto time trace restore time interval to 720

N01-M107-0701.40.1D-C> trce 7 1 CRM L5 slot 7 cpu 1 app CRM trace level = L1 L2 L3 L4 L5 L6 L7 L8 Do you want to change CRM trace level of the slot 7 cpu 1 to L1 -- L5 ? (Y/N) y TrcEnable Done !

Starting MEGACO and ALCAP traces on PAC 7 CPU 0

N01-M107-0701.40.1D-C> N01-M107-0701.40.1D-C> meg 0 0 Subsystem values: gen=0 sm=1 mib=2 sck=3 cfg=4 Enter subsystem: 3 Filter level values: =0 =1 =2 =3 =4 Enter new level: 0 N01-M107-0701.40.1D-C> trce 7 0 ALCAP L3

Starting CRM traces on PAC 7 CPU 1

N01-M107-0701.40.1D-Telnet> send 7,1:connect N01-M207-0701.40.1A-C>

N01-M207-0701.40.1A-C> msgt sccp egcp alcap

Are you sure you want to modify message trace? [y/n] : y

Msg trace on primitive type : EGCP+SCCP+ALCAP Trace mode : Text **** To activate message trace, enable CRM level 3 trace on CPU 0

Thanks, Mai

-------------------------------------------------------------------------------From: Walter Papili [mailto:Walter.Papili@EU.NEC.COM] Sent: Thursday, April 10, 2008 3:32 PM To: Pratik Kapadia; Mai Gregory Cc: Van-orden, Jon; Antonio Coricciati; Luisa Pianta; davide budicin Subject: MTM call failure Importance: High

Hi all, thank you for the support, we were succesfull in restore the signalling between INC and MGW and UE were able to camp on Femtocell. Still we have a problem with the CS call establishment, in case of a Mobile to M obile call. Could it be related to the issue we faced in these days in TI lab? Please find the attached logs

Regards

Walter Papili UTRAN System Engineer Systems & Infrastructures Division NEC Italia srl Via L. Da Vinci 97 20090 Trezzano S/N (MI) Phone: +39 02 48415 458 Fax: +39 02 48415 451 Mobile: +39 335 1335734 NEW E-mail address: walter.papili@eu.nec.com

******************************************************************************** *************************************************************************** This message and any attachments are intended for the use of the addressee and m

ay contain information that is confidential and privileged or otherwise protecte d from disclosure. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is not authorised. If you are not the in tended recipient, please immediately notify the sender and delete this message a nd the attachment from your system. Opinions, conclusions and other information contained in this message that do not relate to the official business of NEC Ita lia Srl, its parents or subsidiaries, shall not be understood as endorsed by NEC Italia Srl, its parent or subsidiaries and no liability will be accepted for th e same. Any legally binding agreement resulting from its contents must be made s eparately in a printed medium. Le informazioni contenute in questa comunicazione (ed in ogni allegato eventualm ente presente) sono confidenziali, e si intendono riservate al solo destinatario . E vietato ai soggetti diversi dai destinatari di effettuare qualsiasi uso, diff ondere, copiare o distribuire le informazioni o i dati contenuti nella presente comunicazione, ai sensi dell'art 616 c.p. e della vigente normativa italiana in tema di protezione dei dati personali. Se questa comunicazione arrivata per erro re, Vi preghiamo di informarci chiamando il numero 02.484151 o rispondendo a que sta mail, e di cancellarla dal vostro sistema informativo. Opinioni, dichiarazio ni ed informazioni contenute nel presente messaggio che non attengono al normale svolgimento delle attivit di NEC Italia Srl, non potranno essere considerate com e vincolanti per NEC Italia Srl, e nessuna responsabilit sar riconosciuta per le s tesse. Ogni accordo contrattuale risultante dalla presente comunicazione dovr ess ere redatta e siglata in cartaceo.

Click here to report this email as spam.