Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
Bookmark
|
Subscribe
|
4599
Views
0
Helpful
24
Replies

CME Sip-ua outbound calls problems with messagenet VOIP provider

_Mike_
Level 1
Level 1

‎05-26-2016 10:22 AM - edited ‎03-17-2019 07:03 AM

Hi all,

I have an existing old cme 7.1 based on a UC540 with this topology connections:   cme____firewall____adslrouter___SIPprovider

Once bought the phone number, the provider has sent me the following parameters: URI, Password and SIP Server  (sip.messagenet.it:5061)

I configured a sip-ua profile to permit all my cisco phones to place voip calls via "messagenet" provider.

Doing tests with my CIPC softphone, I can receive calls configuring the command  "number 112 secondary 5406042832 no-reg primary" under the ephone-dn, but trying to make outbound calls I got always the fast busy tone.

What am I doing wrong, can anyone help me?

Here is my "debug ccsip messages" and the cme conf. in attach, thank you in advance.

035188: May 25 10:34:41.107: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:9347xxxxx9@sip.messagenet.it:5061 SIP/2.0
Date: Wed, 25 May 2016 10:34:41 GMT
Call-Info: <sip:192.168.2.254:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
Allow-Events: telephone-event
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Remote-Party-ID: "IFI Tests" <sip:112@192.168.2.254>;party=calling;screen=no;privacy=off
Cisco-Guid: 455890549-563810790-2880145261-787559590
Timestamp: 1464172481
Content-Length: 303
User-Agent: Cisco-SIPGateway/IOS-12.x
To: <sip:9347xxxxx9@sip.messagenet.it>
Contact: <sip:112@192.168.2.254:5060>
Expires: 180
Content-Disposition: session;handling=required
Content-Type: application/sdp
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33B2040
CSeq: 101 INVITE
Max-Forwards: 70

v=0
o=CiscoSystemsSIP-GW-UserAgent 2357 9567 IN IP4 192.168.2.254
s=SIP Call
c=IN IP4 192.168.2.254
t=0 0
m=audio 18002 RTP/AVP 0 8 18 100
c=IN IP4 192.168.2.254
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194

035189: May 25 10:34:41.131: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 407 Proxy Authentication Required
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
To: <sip:9347xxxxx9@sip.messagenet.it>;tag=ac2f3091de46227321b1af258e10b75e-3c84
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33B2040;rport=56043;received=79.58.183.41
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="sip.messagenet.it", nonce="V0WA61dFf78BY5IQto2DBbbF2rNhKuIkCKrgqfvMxS4snvgPYozQYGCmlkOC", qop="auth"
Server: sip.messagenet.it SIP Proxy
Content-Length: 0
Warning: 392 212.97.59.76:5061 "Noisy feedback tells:  pid=24839 req_src_ip=79.58.183.41 req_src_port=56043 in_uri=sip:9347xxxxx9@sip.messagenet.it:5061 out_uri=sip:9347xxxxx9@sip.messagenet.it:5061 via_cnt==1"


035190: May 25 10:34:41.135: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:9347xxxxx9@sip.messagenet.it:5061 SIP/2.0
Date: Wed, 25 May 2016 10:34:41 GMT
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
Allow-Events: telephone-event
Content-Length: 0
To: <sip:9347xxxxx9@sip.messagenet.it>;tag=ac2f3091de46227321b1af258e10b75e-3c84
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33B2040
CSeq: 101 ACK
Max-Forwards: 70


035191: May 25 10:34:41.135: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:9347xxxxx9@sip.messagenet.it:5061 SIP/2.0
Date: Wed, 25 May 2016 10:34:41 GMT
Call-Info: <sip:192.168.2.254:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
Allow-Events: telephone-event
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Remote-Party-ID: "IFI Tests" <sip:112@192.168.2.254>;party=calling;screen=no;privacy=off
Cisco-Guid: 455890549-563810790-2880145261-787559590
Timestamp: 1464172481
Content-Length: 303
User-Agent: Cisco-SIPGateway/IOS-12.x
Proxy-Authorization: Digest username="5406042832",realm="sip.messagenet.it",uri="sip:9347xxxxx9@sip.messagenet.it:5061",response="bb7956866aec9477983c390c07e5d74a",nonce="V0WA61dFf78BY5IQto2DBbbF2rNhKuIkCKrgqfvMxS4snvgPYozQYGCmlkOC",cnonce="51E8C7B7",qop=auth,algorithm=md5,nc=00000001
To: <sip:9347xxxxx9@sip.messagenet.it>
Contact: <sip:112@192.168.2.254:5060>
Expires: 180
Content-Disposition: session;handling=required
Content-Type: application/sdp
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33C2583
CSeq: 102 INVITE
Max-Forwards: 70

v=0
o=CiscoSystemsSIP-GW-UserAgent 2357 9567 IN IP4 192.168.2.254
s=SIP Call
c=IN IP4 192.168.2.254
t=0 0
m=audio 18002 RTP/AVP 0 8 18 100
c=IN IP4 192.168.2.254
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194

035192: May 25 10:34:41.159: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Auth/From Username Matching Policy Failed
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
To: <sip:9347xxxxx9@sip.messagenet.it>;tag=98df93dff07c6bc0cd4e22344f9aa5a7.101e
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33C2583;rport=56043;received=79.58.183.41
CSeq: 102 INVITE
Server: sip.messagenet.it SIP Proxy
Content-Length: 0
Warning: 392 212.97.59.76:5061 "Noisy feedback tells:  pid=24845 req_src_ip=79.58.183.41 req_src_port=56043 in_uri=sip:9347xxxxx9@sip.messagenet.it:5061 out_uri=sip:9347xxxxx9@sip.messagenet.it:5061 via_cnt==1"


035193: May 25 10:34:41.163: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:9347xxxxx9@sip.messagenet.it:5061 SIP/2.0
Date: Wed, 25 May 2016 10:34:41 GMT
From: "05xxxxxxx2" <sip:112@sip.messagenet.it>;tag=EDCEE9AC-26E6
Allow-Events: telephone-event
Content-Length: 0
To: <sip:9347xxxxx9@sip.messagenet.it>;tag=98df93dff07c6bc0cd4e22344f9aa5a7.101e
Call-ID: 1F5A5458-219B11E6-ABB0876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bK3E33C2583
CSeq: 102 ACK
Max-Forwards: 70

1 person had this problem
Labels:
cme_11.txt
Preview file
13 KB
0 Helpful
24 Replies 24

Vivek Batra
VIP Alumni
VIP Alumni
In response to _Mike_

‎06-22-2016 05:31 AM

Hi Mike,

From Xlite, you have shared only screen shot. Can you please share complete REGISTER message from Xlite?

- Vivek

0 Helpful

_Mike_
Level 1
Level 1
In response to Vivek Batra

‎06-22-2016 06:16 AM

Hi Vivek, thanks for your attention.

The screenshot is the sip logs from wireshark for the register message of x-lite.

Now I share the logs from x-lite tool for the register message of x-lite.

I hope I have understood your request.

I'm available for any further information. Thanks again.

- Mike

outputlog.txt
Preview file
167 KB
0 Helpful

Vivek Batra
VIP Alumni
VIP Alumni
In response to _Mike_

‎06-22-2016 06:28 AM

Hi Mike,

I got it what I wanted to know from Xlite. Now share the REGISTER message as per latest config what you are sending to Telco from Cisco VG.

- Vivek

0 Helpful

_Mike_
Level 1
Level 1
In response to Vivek Batra

‎06-22-2016 07:22 AM

Here is the sip register messages with the latest cme config.

0 Helpful

_Mike_
Level 1
Level 1
In response to _Mike_

‎06-27-2016 01:05 AM

Hi Vivek and Mohit,

did I provide all the required info?

do you have any suggestion comparing the two log files?

Thank you.

0 Helpful

MOHIT SINGH
Level 1
Level 1
In response to _Mike_

‎07-03-2016 12:54 AM

Hi Mike,

I compared the messages and found that the Register Message sent by gateway does not have correct number in FROM field. It should be like X-lite below

To: "Zamboni Test"<sip:5406042832@sip.messagenet.it:5061>

From: "Zamboni Test"<sip:5406042832@sip.messagenet.it:5061>;tag=68b7e779

Currently the gateway is sending FROM as "107".

From: <sip:107@sip.messagenet.it>;tag=4002ED34-1C0C

Do you have SIP phones in setup as well because the config you shared only shows SCCP? For outbound calls send calling number (from) as "5406042832" instead of "05406042832"

0 Helpful

_Mike_
Level 1
Level 1
In response to MOHIT SINGH

‎07-08-2016 07:28 AM

Hi Mohit and thanks for your attention.

I don't have SIP Phones, I've only SCCP.

My target is to place SIP calls from any SCCP phones registered in this cme. I don't know why calls still going out FROM: <sip:107@sip.messagenet.it> where 107 is the directory number of the cipc I'm using for tests.

This is for sure one of the problems I need help to solve.

For outbound calls send calling number (from) as "5406042832" instead of "05406042832"

From what does this behavior depends? Does it depends from dial peer that follows?

dial-peer voice 111 voip
 description USCITA TRAMITE LINEA VOIP
 translation-profile outgoing 10
 destination-pattern 9T
 voice-class codec 1
 session protocol sipv2
 session target sip-server
 session transport udp
 incoming called-number 05431796482
 dtmf-relay sip-notify
 no vad

0 Helpful

Deepak Mehta
VIP Alumni
VIP Alumni
In response to _Mike_

‎07-08-2016 07:54 AM

Modify the rule 10 to below so that we send only 5406042832 which is same as xlite is sending.

voice translation-rule 10

    rule 1 /.*/ /5431796482/

0 Helpful

_Mike_
Level 1
Level 1
In response to Deepak Mehta

‎07-08-2016 08:26 AM

Hi Deepak,

in attach the new "debug ccsip messages" after I have modified the rule 10 like your suggestion.

The outboud calls still fail with fast busy tone.

But the strange behavior maybe we have we have to analyze is why if I try to place a call with my ip communicator, the cme still try to place call continuously from any sccp phone.... how u can see from the debud log:

From: <sip:106@sip.messagenet.it>;tag=D1620690-29B

....

From: <sip:107@sip.messagenet.it>;tag=D1620690-29B

....

From: <sip:104@sip.messagenet.it>;tag=D1620690-29B

....

From: <sip:108@sip.messagenet.it>;tag=D1620690-29B

....

From: <sip:110@sip.messagenet.it>;tag=D1620690-29B

...

0 Helpful

Deepak Mehta
VIP Alumni
VIP Alumni
In response to _Mike_

‎07-08-2016 08:43 AM

After you sent the inital invite with SDP i dont see a response from the service provider.Can you confirm with SP if they are seeing the invite reaching to them .

I can see you have a firewall as well so make sure it is not blocking any SIP  traffic in outbound direction.

Other SCCP phones are not placing calls but sending continuous register messages to the SIP provider which looks normal to me.

++++++++++++++++++++++++++++++++

Sent:
INVITE sip:93475471199@sip.messagenet.it:5061 SIP/2.0
Date: Fri, 08 Jul 2016 15:11:52 GMT
Call-Info: <sip:192.168.2.254:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
From: "05431796482" <sip:5431796482@sip.messagenet.it>;tag=D16219C8-21E7
Allow-Events: telephone-event
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Remote-Party-ID: "IFI Tests" <sip:5431796482@192.168.2.254>;party=calling;screen=no;privacy=off
Cisco-Guid: 504154354-1146425830-2581825389-787559590
Timestamp: 1467990712
Content-Length: 302
User-Agent: Cisco-SIPGateway/IOS-12.x
To: <sip:93475471199@sip.messagenet.it>
Contact: <sip:5431796482@192.168.2.254:5060>
Expires: 180
Content-Disposition: session;handling=required
Content-Type: application/sdp
Call-ID: 226C39D8-445511E6-99E8876D-2EF134A6@192.168.2.254
Via: SIP/2.0/UDP 192.168.2.254:5060;branch=z9hG4bKEF0AA20B9
CSeq: 101 INVITE
Max-Forwards: 70

v=0
o=CiscoSystemsSIP-GW-UserAgent 281 6885 IN IP4 192.168.2.254
s=SIP Call
c=IN IP4 192.168.2.254
t=0 0
m=audio 18656 RTP/AVP 0 8 18 100
c=IN IP4 192.168.2.254
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8

0 Helpful
Customers Also Viewed These Support Documents
li.common.scroll-to.top