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

CUCME Not Incoming Calls, Outgoing calls ok

Hello everybody,

i am configuring a CUCME with SIP trunk, i can make calls to outside but i can´t recieve any from outside, this is my second time a configure with SIP

i´ve used the command debug voice dialpeer all to check was going on, but i can´t find the problem.

this is my config:


ip host sip-server A.B.C.D

!

voice service voip

ip address trusted list

  ipv4 A.B.C.D 255.255.255.252

!

  voice translation-rule 1

rule 1 /325277\(\)/ /1\1/

!

voice translation-profile IN

translate called 1

!

dial-peer voice 1 voip

description **Incoming Call from SIP Trunk**

translation-profile incoming IN

session protocol sipv2

session target sip-server

incoming called-number .

voice-class codec 1 

voice-class sip dtmf-relay force rtp-nte

dtmf-relay rtp-nte

no vad

!

ephone-dn  1

number 100

description RECEPTION

!

ephone  2

mac-address AAAA.BBBB.CCCC

ephone-template 1

type 7942

keep-conference

button  1:1

NOTE: IP Address are hidden, just for security


These are the output of my debug/tests:

#test voice translation-rule 1 32527700

Matched with rule 1

Original number: 32527700       Translated number: 100

Original number type: none      Translated number type: none

Original number plan: none      Translated number plan: none

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Calling Number=32527700, Called Number=32527700, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=32527700

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Dial String=32527700, Expanded String=32527700, Calling Number=32527700T

   Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=32527700, saf_enabled=1, saf_dndb_lookup=1, dp_result=-1

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

   Result=NO_MATCH(-1)

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=59513212, Called Number=, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_ANSWER; Calling Number=59513212

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=59513212T

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_ORIGINATE; Calling Number=59513212

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=59513212T

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

*Jan 29 16:17:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeer:exit@6704

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Calling Number=59513212, Called Number=32527700, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_VIA_URI; URI=sip:A.B.C.D:5060

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_REQUEST_URI; URI=sip:32527700@E.F.G.H:5060;user=phone

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_TO_URI; URI=sip:32527700@I.J.K.L;user=phone

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_FROM_URI; URI=sip:59513212@X.Y.Z.Z;user=phone

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Result=-1

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=32527700

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchCore:

   Dial String=32527700, Expanded String=32527700, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/MatchNextPeer:

   Result=Success(0); Incoming Dial-peer=1 Is Matched

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchPeertype:exit@6076

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

*Jan 29 16:17:14: //-1/F0EA1F0180EB/DPM/dpAssociateIncomingPeerSPI:exit@6655

Can Anyone help me???

Thanks in Advance!!!

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

CUCME Not Incoming Calls, Outgoing calls ok

I looked on the other call leg of the SIP messages , here is the fault for call where Incoming is getting failed due to session timer is too small recieved from the SBC (provider)

Call ID:

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

INVITE RECEIEVED FROM SBC--SIP

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:32527700@(WAN):5060;user=phone SIP/2.0

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Max-Forwards: 70

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R601

Session-Expires: 300

Min-SE: 90

Contact: <59513212>

Content-Length: 376

Content-Type: application/sdp

v=0

o=HuaweiSoftX3000 4507886 4507886 IN IP4 (SIP_SERVER)

s=Sip Call

c=IN IP4 (SIP_SERVER)

t=0 0

m=audio 11554 RTP/AVP 8 0 18 4 2 98 98 98

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=rtpmap:4 G723/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:98 G726-40/8000

a=rtpmap:98 G726-32/8000

a=rtpmap:98 G726-24/8000

a=ptime:20

a=fmtp:18 annexb=no

In response CME SENDs 422 response

Sent:

SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>;tag=4CD1E84-2094

Date: Wed, 29 Jan 2014 22:53:19 GMT

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

CSeq: 1 INVITE

Allow-Events: telephone-event

Min-SE:  1800

Server: Cisco-SIPGateway/IOS-15.2.4.M

Content-Length: 0

as per rfc

  If the Session-Expires interval is too low for a proxy (i.e., lower

   than the value of Min-SE that the proxy would wish to assert), the

   proxy rejects the request with a 422 response.  That response

   contains a Min-SE header field identifying the minimum session

   interval it is willing to support.  The UAC will try again, this time

   including the Min-SE header field in the request.  The header field

   contains the largest Min-SE header field it observed in all 422

   responses previously received.  This way, the minimum timer meets the

   constraints of all proxies along the path.

http://www.cisco.com/en/US/docs/ios/voice/sip/configuration/guide/sip_cg-msg_tmr_rspns.html#wp1056968

422 Response Message

If the value of the Session-Expires header is too small, the UAS or proxy rejects the call with a 422 Session Timer Too Small response message. With the 422 response message, the proxy or UAS  includes a Min-SE header indicating the minimum session value it can  accept. The UAC may then retry the call with a larger session timer  value.

If a 422 response message is received after an INVITE request, the UAC can retry the INVITE.

there is two way to fix this issue

1) asked the SBC (your SIP provider) change the value and send standards value in the SIP invite in Session expires

2) Change the value of the Min-SE on the CME with command

run this Global Config on CME

voice service voip

allow connection sip to sip

sip

min-se 90

Br,

Nadeem

Please rate all useful post.

Br, Nadeem Please rate all useful post.
6 REPLIES
Cisco Employee

CUCME Not Incoming Calls, Outgoing calls ok

Is this a complete logs, i can see only the incoming dial-peer matched ie 1 and nothing .

Can you please collect below output and make a test calls

Debug cssip messages

debug voice ccapi inout

debug voice dialpeer inout


Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.
New Member

CUCME Not Incoming Calls, Outgoing calls ok

Thanks, these are the output

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:32527700@(WAN):5060;user=phone SIP/2.0

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Max-Forwards: 70

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R601

Session-Expires: 300

Min-SE: 90

Contact: <59513212>

Content-Length: 376

Content-Type: application/sdp

v=0

o=HuaweiSoftX3000 4507886 4507886 IN IP4 (SIP_SERVER)

s=Sip Call

c=IN IP4 (SIP_SERVER)

t=0 0

m=audio 11554 RTP/AVP 8 0 18 4 2 98 98 98

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=rtpmap:4 G723/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:98 G726-40/8000

a=rtpmap:98 G726-32/8000

a=rtpmap:98 G726-24/8000

a=ptime:20

a=fmtp:18 annexb=no

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Calling Number=32527700, Called Number=32527700, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=32527700

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

   No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=32527700, saf_enabled=1, saf_dndb_lookup=1, dp_result=-1

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

   Result=NO_MATCH(-1)

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=59513212, Called Number=, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

*Jan 29 16:53:19: //-1/FB88A7CE80F0/DPM/dpAssociateIncomingPeerCore:

   Calling Number=59513212, Called Number=32527700, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 29 16:53:19: //-1/FB88A7CE80F0/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1

*Jan 29 16:53:19: //-1/FB88A7CE80F0/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>;tag=4CD1E84-2094

Date: Wed, 29 Jan 2014 22:53:19 GMT

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

CSeq: 1 INVITE

Allow-Events: telephone-event

Min-SE:  1800

Server: Cisco-SIPGateway/IOS-15.2.4.M3

Content-Length: 0

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:32527700@(WAN):5060;user=phone SIP/2.0

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>;tag=4CD1E84-2094

CSeq: 1 ACK

Max-Forwards: 70

Content-Length: 0

*Jan 29 16:53:31: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

REGISTER sip:(SIP_SERVER):5060 SIP/2.0

Via: SIP/2.0/UDP (WAN):5060;branch=z9hG4bK3B11F0F

From: <103>;tag=4CD4D7C-1634

To: <103>

Date: Wed, 29 Jan 2014 22:53:31 GMT

Call-ID: 3017EE62-885411E3-80B4FEFC-CAA82B4A

User-Agent: Cisco-SIPGateway/IOS-15.2.4.M3

Max-Forwards: 70

Timestamp: 1391036011

CSeq: 66 REGISTER

Contact: <103>

Expires:  3600

Supported: path

Content-Length: 0

*Jan 29 16:53:31: //973/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 400 Bad Request

Via: SIP/2.0/UDP (WAN):5060;branch=z9hG4bK3B11F0F

Call-ID: 3017EE62-885411E3-80B4FEFC-CAA82B4A

From: <103>;tag=4CD4D7C-1634

To: <103>;tag=f2056e8e

CSeq: 66 REGISTER

Content-Length: 0

I´ve replaced the IP Adress for (SIP_SERVER) / (WAN) / SIP_SERVER_INTERNAL

Thank you

Cisco Employee

CUCME Not Incoming Calls, Outgoing calls ok

Hello ,

You are recieving 400 BAD REQUEST from Peer node. as per RFC 3261

21.4.1 400 Bad Request

   The request could not be understood due to malformed syntax.  The

   Reason-Phrase SHOULD identify the syntax problem in more detail, for

   example, "Missing Call-ID header field".

You can check with ITSP'/ provider with this above error to fix this issue. AFAIK its not an issue with your device


Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.
Cisco Employee

CUCME Not Incoming Calls, Outgoing calls ok

I looked on the other call leg of the SIP messages , here is the fault for call where Incoming is getting failed due to session timer is too small recieved from the SBC (provider)

Call ID:

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

INVITE RECEIEVED FROM SBC--SIP

*Jan 29 16:53:19: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:32527700@(WAN):5060;user=phone SIP/2.0

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>

CSeq: 1 INVITE

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER

Max-Forwards: 70

Supported: 100rel,timer

User-Agent: Huawei SoftX3000 V300R601

Session-Expires: 300

Min-SE: 90

Contact: <59513212>

Content-Length: 376

Content-Type: application/sdp

v=0

o=HuaweiSoftX3000 4507886 4507886 IN IP4 (SIP_SERVER)

s=Sip Call

c=IN IP4 (SIP_SERVER)

t=0 0

m=audio 11554 RTP/AVP 8 0 18 4 2 98 98 98

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=rtpmap:4 G723/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:98 G726-40/8000

a=rtpmap:98 G726-32/8000

a=rtpmap:98 G726-24/8000

a=ptime:20

a=fmtp:18 annexb=no

In response CME SENDs 422 response

Sent:

SIP/2.0 422 Session Timer too small

Via: SIP/2.0/UDP (SIP_SERVER):5060;branch=z9hG4bK776928550196f0d843ca0b092

From: <59513212>;tag=6e8b9968-CC-25

To: <32527700>;tag=4CD1E84-2094

Date: Wed, 29 Jan 2014 22:53:19 GMT

Call-ID: SBC9722bb53005161bf8cca630444260574@SoftX3000

CSeq: 1 INVITE

Allow-Events: telephone-event

Min-SE:  1800

Server: Cisco-SIPGateway/IOS-15.2.4.M

Content-Length: 0

as per rfc

  If the Session-Expires interval is too low for a proxy (i.e., lower

   than the value of Min-SE that the proxy would wish to assert), the

   proxy rejects the request with a 422 response.  That response

   contains a Min-SE header field identifying the minimum session

   interval it is willing to support.  The UAC will try again, this time

   including the Min-SE header field in the request.  The header field

   contains the largest Min-SE header field it observed in all 422

   responses previously received.  This way, the minimum timer meets the

   constraints of all proxies along the path.

http://www.cisco.com/en/US/docs/ios/voice/sip/configuration/guide/sip_cg-msg_tmr_rspns.html#wp1056968

422 Response Message

If the value of the Session-Expires header is too small, the UAS or proxy rejects the call with a 422 Session Timer Too Small response message. With the 422 response message, the proxy or UAS  includes a Min-SE header indicating the minimum session value it can  accept. The UAC may then retry the call with a larger session timer  value.

If a 422 response message is received after an INVITE request, the UAC can retry the INVITE.

there is two way to fix this issue

1) asked the SBC (your SIP provider) change the value and send standards value in the SIP invite in Session expires

2) Change the value of the Min-SE on the CME with command

run this Global Config on CME

voice service voip

allow connection sip to sip

sip

min-se 90

Br,

Nadeem

Please rate all useful post.

Br, Nadeem Please rate all useful post.
New Member

CUCME Not Incoming Calls, Outgoing calls ok

Thank you, thank you so much!!!!

voice service voip

sip

min-se 90

That line fixed the issue

Regards!

Cisco Employee

CUCME Not Incoming Calls, Outgoing calls ok

You are most welcome:-)

Br,
Nadeem 

Please rate all useful post.

Br, Nadeem Please rate all useful post.
545
Views
5
Helpful
6
Replies
CreatePlease login to create content