About stillnick

stillnick · 02-04-2021

Hi all.I have an issue that's been driving me crazy since last week. My SIP provider is sending the INVITE package with wrong sip number as you can see bellow:Received:INVITE sip:765617@10.1.222.2:5060 SIP/2.0 (should be 0893540111)v:SIP/2.0/UDP 27.1...

stillnick · 02-01-2021

Hi. Does anyone know why my SIP Provider is not sending me the right called number? Instead it is sending me my Client ID. This is the debug:Feb 1 2021 16:08:37.740 AWST: //77372/8597BD2B82F2/CCAPI/ccIFCallSetupRequestPrivate:Interface=0x3ECC1278, In...

stillnick · 10-11-2019

Hi community. I'm having a problem with a Cisco500-to-Cisco500 family I had configured as site-to-site. Everything was working until we changed ISP in one of the sites. The old ISP was giving me a static public IP which was working like a charm. On t...

stillnick · 02-07-2021

Just coming back to post what I did to fix this issue. On incoming dial-peer (dial-peer 9 voip) I changed the following line. voice-class sip profiles 1TOvoice-class sip profiles 1 incoming I don't know why, but for some reason CUBE wasn't applying m...

stillnick · 02-03-2021

Hi Scott, thanks for you help. This dial-peer is a temporary one that I've created to send these "weird" incoming calls to my CUCM so I wouldn't lose any calls till I fix this. It will be removed when I get the right "called number" from PSTN. Thank...

stillnick · 02-01-2021

Sorry Shalid, I must have missed something. Here will go the full debug. Full conf file attached as well. Feb 2 2021 08:46:00.363 AWST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:NOTIFY sip:765617@10.1.222.2:5060 SIP/2.0v:SIP/2.0/UDP 27.127.2...

stillnick · 02-01-2021

Hi all. Thanks again for the help. Here will go 2 files with configuration and debug + the debug message bellow. Feb 2 2021 07:48:02.132 AWST: //96820/C1621E778782/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 10.1.100.200:5060...

stillnick · 02-01-2021

Hi Shalidm thanks for replying to me. I did all mentioned checks and I'm still getting my account ID instead of the phone number. SP provider tested SIP trunk in one of their router and it is working as expected. Here is another debug that shows this...

Member Since	‎10-11-2019 07:05 AM
Date Last Visited	‎02-10-2021 12:15 AM
Posts	10
Total Helpful Votes Received	5

User Statistics

User Activity

Change INVITE package header with - Conditional SIP Profiles

Problem in SIP-UA called Number given by SIP provider.

IPSEC VPN stopped working after ISP change

Re: Change INVITE package header with - Conditional SIP Profiles

Re: Problem in SIP-UA called Number given by SIP provider.

Re: Problem in SIP-UA called Number given by SIP provider.

Re: Problem in SIP-UA called Number given by SIP provider.

Re: Problem in SIP-UA called Number given by SIP provider.