Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CME between Lync2013 and PSTN

Greetings.

I have:

2811 running CME 8.5 (IOS 15.1(3)T3)

Lync 2013

Most desk endpoints are Cisco phones (7940's, 7960's).

2811 has FXO ports for POTS connection to PSTN

I'm using Lync for desktop/soft clients.

I can dial to the Cisco phones.  I CAN'T dial from a Cisco phone to a Lync client yet either (different problem, I think)

I am unable to dial from a Lync client "through" the CME to PSTN.

Any suggestions on what the dial-peer needs to look like on the Cisco?

Are there any guides on a simple config similar to this?

Thanks!

Everyone's tags (1)
6 REPLIES

Re:CME between Lync2013 and PSTN

Hi
U need to have a sip trunk between cme n lync



Sent from Cisco Technical Support Android App

New Member

Re:CME between Lync2013 and PSTN

Can yo provide a little more information (or links to guides) on how configure that?

I do have 2 dial peer's in CME - one for calls FROM Lync and another for calls TO Lync.

As mentioned, I can call from Lync client to SME phones, but not the other way, nor from Lync clients through to PSTN.

I have 2 dialplans on Lync for calls to CME phones and through CME to PSTN.  Both "test" fine on the Lync side.

Thanks in advance!

CME between Lync2013 and PSTN

Please make a test call from Cisco to Lync and collect 'debug voice ccapi inout & debug ccsip message' and also provide the CME running configuration.

//Suresh Please rate all the useful posts.
New Member

CME between Lync2013 and PSTN

Will do, but note from OP that I'm also having issue dialing from Lync through CME to PSTN.

It seems there are 2 separate issues.

Lync --> CME --> PSTN

I think this has to do with the dial-peer on CME for incoming calls from Lync which need to be redirected to a voice-port.

CME --> Lync

debugs requested may identify this issue.

Thanks again.

New Member

CME between Lync2013 and PSTN

Here is a sanitized ccsip debug - 400 bad request?

Note: the 192.160.254.13 is a GRE tunnel between the lync server and the CME router.

SIP/2.0 100 Trying

FROM: "David Kiernan"<105>;tag=FE68C844-208

TO: <>

CSEQ: 101 INVITE

CALL-ID: 91575B65-612C11E3-9958A2D3-93B2F889@192.168.254.13

VIA: SIP/2.0/TCP 192.168.254.13:5060;branch=z9hG4bK41BC23AF

CONTENT-LENGTH: 0

TIMESTAMP: 1386719379

018727: Dec 10 17:49:39.692 CDT: //58462/90B32AF39953/SIP/Info/sipSPICheckResponseExt: INVITE response with no RSEQ -       disable IS_REL1XX

018728: Dec 10 17:49:39.696 CDT: //58462/90B32AF39953/SIP/State/sipSPIChangeState: 0x4ACEAEF0 : State change from (STA      TE_SENT_INVITE, SUBSTATE_NONE)  to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)

018729: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type r      eturned: 2 for event 1

018730: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x4A00D318

018731: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessNewConnMsg: gConnTab=0x4A0      0D318, addr=192.168.150.14, port=5060, local_addr=, connid=4, transport=TCP

018732: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite Dialog

018733: Dec 10 17:49:39.888 CDT: //58462/90B32AF39953/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 400 Bad Request

FROM: "David Kiernan"<105>;tag=FE68C844-208

TO: <>;epid=B53A9D78CB;tag=af94da49bc

CSEQ: 101 INVITE

CALL-ID: 91575B65-612C11E3-9958A2D3-93B2F889@192.168.254.13

VIA: SIP/2.0/TCP 192.168.254.13:5060;branch=z9hG4bK41BC23AF

CONTENT-LENGTH: 0

SERVER: RTCC/5.0.0.0 MediationServer

CME between Lync2013 and PSTN

400 Bad Request indicates that the initial invite sent from Cisco to Lync is not supported by Lync. We need to check the complete sip logs to know which field(header/sdp) in the Invite is not supported.

Also it seems Lync doesn't support Rel1xx response. You may try disabling it under SIP config n check the behavior.

If not working after disabling the rel1xx, please collect debug ccsip message n debug voice ccapi inout for a test call along with the running config.

//Suresh Please rate all the useful posts.
377
Views
0
Helpful
6
Replies