cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1327
Views
0
Helpful
4
Replies

Problem with sip trunk between CCM and Huawei through Cisco ASA5520

ugabichipaopao
Level 1
Level 1

Hello,

I have a next problem

During SIP conversation ASA is changing  the ip address of CCM to corresponding name in ASA configuration inside the SIP packet:

To:  <sip:443230282@Server_CCM1;user=phone>

ASA name configuration:

name x.y.z.h Server_CCM1

But it should be without any changes like that: To:  <sip:443230282@x.y.z.h;user=phone>. Because of that session cant be established. Remote SIP peer gives an error "Bad Request - 'Malformed/Missing URL"

When name was deleted  in ASA "no name x.y.z.h Server_CCM1" we have no any problem with  SIP initialization and call proccesing.

We are going to upgrade ASA from 8.2 to 8.3 and it seems that we will have the same problem because object will be created automaticly  in new version (we are using a NAT) and we will not be able to delete an object like we did in version 8.2.

What configuration in ASA version 8.3 should be done to avoid this issue.

P.S Detailed debug from Huawei in attachment.

Thank you.

2 Accepted Solutions

Accepted Solutions

fadlouni
Level 1
Level 1

Hi.

depending on your config, you might be hitting CSCta16361, this is fixed in 8.2(4)

if you can confirm it's still happening in latest 8.2 release, then a TAC case needs to be opened so investigation is done and a new bug is opened.

if you've tested 8.2(4) already and it's still doing the same, then a TAC Service Request should be opened for more investigation and possibly opening a new defect.

Best regards,

Fadi.

does  this answer your question? if yes please mark it resolved.

View solution in original post

Thanks Maxim.

glad i could help. would be nice if you can mark this thread as answered.

Regards,

Fadi.

View solution in original post

4 Replies 4

fadlouni
Level 1
Level 1

Hi.

depending on your config, you might be hitting CSCta16361, this is fixed in 8.2(4)

if you can confirm it's still happening in latest 8.2 release, then a TAC case needs to be opened so investigation is done and a new bug is opened.

if you've tested 8.2(4) already and it's still doing the same, then a TAC Service Request should be opened for more investigation and possibly opening a new defect.

Best regards,

Fadi.

does  this answer your question? if yes please mark it resolved.

Hi Fadi!

Thank you for help. With version 8.2(4) sip trunk works well. Problem solved.

Thanks for the quick help!

BR,

Maxim

Thanks Maxim.

glad i could help. would be nice if you can mark this thread as answered.

Regards,

Fadi.

Hi,

I experiencing problems with SIP trunk actually, the supplementary services are not working.

So I want to know what was the version of the CUCM and MSC Huawei you used?

regards,

Antra

Review Cisco Networking for a $25 gift card