configuracion voztelecom en uc540 por cca - Página 2

David Hernanz · ‎02-02-2012

Buenas noches, me gustaria saber si alguien ha conseguido configurar un enlace sip de voztelecom por CCA 3.2. Yo actualmente he configurado el enlace y este me permite realizar llamadas sin problemas pero no me permite recibirlas. He revisado las ACL y aparentemente estan todas bien . No se cual puede ser el problema. un saludo y gracias a todos por anticipado

Leo Salcie Tejeda · ‎02-19-2013

Enrique, el debug esta incompleto...

Please rate all useful posts
Favor calificar todos las respuestas útiles.
_____________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie
MDGDP, CCNA, CCNA Voice certified

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie

ealvarez · ‎02-20-2013

Lo he intantado varias veces pero siempres me sale lo mismo, no sé que puede ser...

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: disabled

Monitor logging: disabled

Buffer logging: level debugging, 19 messages logged, xml disabled,

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 686 message lines logged

Logging Source-Interface: VRF Name:

Log Buffer (5000000 bytes):

000839: Feb 20 13:42:48.793: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.50

000840: Feb 20 13:42:48.873: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.50

ealvarez · ‎02-21-2013

Alguna pista? Estoy un poco desesperado...

Sent from Cisco Technical Support iPhone App

Leo Salcie Tejeda · ‎02-21-2013

Necesito el trace para poder responderte....

Please rate all useful posts
Favor calificar todos las respuestas útiles.
_____________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie
MDGDP, CCNA, CCNA Voice certified

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie

ealvarez · ‎02-22-2013

A ver si esto te vale, es un debug ccsip calls

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

    Console logging: disabled
    Monitor logging: disabled
    Buffer logging: level debugging, 22 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 773 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (5000000 bytes):

000928: Feb 22 17:29:27.248: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.30
000929: Feb 22 17:29:27.328: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.30
000930: Feb 22 17:29:34.680: //-1/E08826E09B4D/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x88A62078
State of The Call        : STATE_DEAD
TCP Sockets Used         : NO
Calling Number           :
Called Number            : 956924975
Source IP Address (Sig ): 192.168.0.85
Destn SIP Req Addr:Port : 94.23.83.177:0
Destn SIP Resp Addr:Port : 94.23.83.177:5060
Destination Name         : 94.23.83.177

000931: Feb 22 17:29:34.680: //-1/E08826E09B4D/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 100
Disconnect Cause (SIP) : 400

David Hernanz · ‎05-16-2013

no se si ya tendras resuelto el tema , en mi caso eran las acl lo arregle poniendo esto

TAI#conf term

TAI(config)#voice source-group CCA_SIP_SOURCE_GROUP_EXTERNAL

TAI(cfg-source-grp)#no access-list 3

TAI(cfg-source-grp)#exit

TAI(config)#exit

TAI#wr

Un saludo

ealvarez · ‎05-17-2013

La verdad es que no, está funcionando todo menos la recepción de llamadas a través del Trunk Sip, te agradezco mucho la respuesta, ¿como se podría hacer a través del CCA?, supongo que esto elimina la access-list 3.

Un saludo.

ealvarez · ‎06-05-2013

Hola Adjunto debug ccsip messages

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: disabled

Monitor logging: disabled

Buffer logging: level debugging, 22 messages logged, xml disabled,

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 304 message lines logged

Logging Source-Interface: VRF Name:

Log Buffer (5000000 bytes):

000290: Jun 5 18:33:35.231: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.66

000291: Jun 5 18:33:35.371: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.66

000292: Jun 5 18:33:40.151: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15183) -> 192.168.0.80(443), 1 packet

000293: Jun 5 18:33:41.419: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49627) -> 192.168.0.80(443), 1 packet

000294: Jun 5 18:33:42.683: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18805) -> 192.168.0.80(443), 1 packet

000295: Jun 5 18:33:43.947: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13182) -> 192.168.0.80(443), 1 packet

000296: Jun 5 18:33:49.491: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 119 packets

000297: Jun 5 18:33:53.183: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15192) -> 192.168.0.80(443), 1 packet

000298: Jun 5 18:33:54.455: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49629) -> 192.168.0.80(443), 1 packet

000299: Jun 5 18:33:55.763: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18818) -> 192.168.0.80(443), 1 packet

000300: Jun 5 18:33:56.987: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13184) -> 192.168.0.80(443), 1 packet

000301: Jun 5 18:34:04.543: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:856924825@62.43.206.102:56214 SIP/2.0

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

Max-Forwards: 70

From: "956059747" <956059747>;tag=as15ae1fa9

To: <856924825>

Contact: <956059747>

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 INVITE

User-Agent: VozGlobal

Date: Wed, 05 Jun 2013 16:31:40 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Remote-Party-ID: "956059747" <956059747>;party=calling;privacy=off;screen=no

Content-Type: application/sdp

Content-Length: 272

v=0

o=root 1516626963 1516626963 IN IP4 94.23.83.177

s=VozGlobal

c=IN IP4 94.23.83.177

t=0 0

m=audio 14058 RTP/AVP 18 8 101

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendrecv

000302: Jun 5 18:34:04.547: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 400 Bad Request - 'Invalid Host'

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

From: "956059747" <956059747>;tag=as15ae1fa9

To: <856924825>;tag=8F9F8-2485

Date: Wed, 05 Jun 2013 16:34:04 GMT

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 INVITE

Allow-Events: telephone-event

Reason: Q.850;cause=100

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

000303: Jun 5 18:34:04.631: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:856924825@62.43.206.102:56214 SIP/2.0

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

Max-Forwards: 70

From: "956059747" <956059747>;tag=as15ae1fa9

To: <856924825>;tag=8F9F8-2485

Contact: <956059747>

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 ACK

User-Agent: VozGlobal

Content-Length: 0

000304: Jun 5 18:34:06.263: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15203) -> 192.168.0.80(443), 1 packet

000305: Jun 5 18:34:07.463: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49631) -> 192.168.0.80(443), 1 packet

000306: Jun 5 18:34:08.791: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18828) -> 192.168.0.80(443), 1 packet

000307: Jun 5 18:34:10.031: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13187) -> 192.168.0.80(443), 1 packet

ealvarez · ‎06-12-2013

Alguna idea?

Gracias.