Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3293
Views
0
Helpful
34
Replies

CUCME do not register, no outbound call

Go to solution
o0chrisb0o
Level 1
Level 1

‎11-11-2019 09:47 AM - edited ‎11-11-2019 10:46 AM

Hi,

I'm pulling my air out since last week. Here's my problem. It has been over a year that I setup a phone system, and everything was working fine. Then I changed my setup last week.

 

My old setup was basically like this:

cucme (2811) ==> ISP Router ==> Twilio (SIP Trunk) (NAT was made directly on the 2811)

 

Now my setup is as follow

cucme (2811) ==> router (1941) ==> PFSense FW (NAT happen here) ==> ISP Router (Bridge Mode) ==> Twilio.

 

What's working:

  • All phones can communicate between them internaly
  • All inbound call works flawlessly

What's not working:

  • Outbound calls

Here's the symptoms when I try to do an outbound call, when a pickup the phone and dial a outside number, I press 9, then I hear the fast dialtone, as usual, then type the number, I see the "Ring Out" on the phone screen, but nothing happen, no sound or click can be heard on the phone.

 

When I check the debug messages, I can see that the systems try to register to Twilio, but I do not receive any response from them. When I check the debug console at Twilio, it seems that they do not even received anything. (I'll include all the logs, pcap (from firewall) and config)

 

I have a feeling that it's related to the NAT, since it was working perfectly when the NAT was made by the 2811, I check for STUN and ALG but I don't know where to start or how it really works.

I would like to get your opinion on the matter, right now it beyond me and I would like to learn from that experience!

 

Looking forward for your help, I'm sure it's a small detail that I overlooked.

Preview file
13 KB
Preview file
25 KB
Preview file
181 KB
0 Helpful
3 Accepted Solutions

Accepted Solutions

Go to solution
o0chrisb0o
Level 1
Level 1
In response to o0chrisb0o

‎03-30-2020 11:08 AM - edited ‎03-30-2020 11:35 AM

Hey Guys,

I wasn't able to work on this matter for a while, but yesterday I've been able to make some significant progress. I find out, by comparing an old working backup configuration with my actual setup that a small diffrence that I overlook and that Twilio picked up this time.

In the translation rules, before, it was configured like this:

rule 1 /1001/ /5345551212/

But before, in my old config it was like this:

rule 1 /1001/ /+15345551212/

But the most significant change that made the whole thing " work " is adding the following, a voice class:

voice class sip-profiles 1
 request INVITE sip-header Contact modify "<sip:user@192.168.20.1:5060>" "<sip:user@my_public_ip:5060>

then call it in the dial-peer:

dial-peer voice 9 voip
 --- snip ---
 voice-class sip profiles 1
 -- snip --
 no vad

I put the word work in quote, although it worked, it takes a good 15-20 seconds before the call is connected and start to ring! You guys have any idea what could cause such a delay? And incoming calls cut after 12 seconds.

 

Thanks!

View solution in original post

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎03-31-2020 10:06 AM - edited ‎03-31-2020 02:07 PM

Hi Tony,

The outgoing call delay is now fixed, I recently changed my DNS servers address and did not change the setting in my configuration, once changed to my new DNS server address, it connected without delay. The delay was caused by the time it took to do the lookup then fall back on 1.1.1.1, my secondary name server.

 

For the incoming calls the problem still there, I'll post the output of the logs a little bit later today.

 

Edit: I do get two-way audio in both case. Added Log Files

Thanks!

View solution in original post

Preview file
19 KB
Preview file
37 KB
0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎04-03-2020 01:43 PM - edited ‎04-03-2020 02:26 PM

Thanks, Tony,

I did not know about this tool. Very handy, so I tested the following statement in my config as well as in the test tool:

voice class sip-profiles 10
  response 200 sip-header Contact modify “<sip:(.*)@192.168.20.1:5060>" "<sip:64.114.20.54:5060>"

Then I call the profile in the `voice service voip` section under the sip configuration like so:

voice service voip
 ip address trusted list
 ---  snip ---
 allow-connections sip to sip
 no supplementary-service sip handle-replaces
 sip
  bind control source-interface FastEthernet0/0.20
  bind media source-interface FastEthernet0/0.20
  registrar server expires max 3600 min 600
  early-offer forced
  sip-profiles 10 ##HERE

Then, it freaking WORKED!!!!! At last! I'm so happy! I want to thank you for all the help you provided to help me troubleshoot this issue.

Ultimately, I will replaced my PFSense firewall with a Cisco ASA5515x so this can be done automatically in the firewall. Because, right now, every time my IP change, I'll need to adjust my config, which is a pain in the butt. Now I can move on to another project!

 

Thank you very much for your help.

View solution in original post

0 Helpful
34 Replies 34

Go to solution
TONY SMITH
Spotlight
Spotlight

‎11-13-2019 07:01 AM

I've no idea about PF Sense, so what I'd suggest is taking a packet capture outside the firewall, between the firewall and the ISP router.  Compare that with your debugs on the router and take it from there.   In my experience most ITSPs don't want you to use an ALG, so it might be worth having a look in PF Sense to see if that can be switched on or off.

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎11-13-2019 06:46 PM

Thanks, I'll have a look, but it was working fine when the CUCME was directly connected to the ISP Router. I might also tried to connect the CUCME directly in the firewall, instead of passing through another router.
0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎11-14-2019 12:13 AM

Although it worked OK before, you must have made a number of changes to CME given that it used to do NAT, and now there's a router and a firewall in the path.   Can you share before and after configurations?  You have an authenticated trunk so until that's registered you will probably not be able to make outbound calls.  Confirm this by checking registration "sh sip-ua register status" and dial-peer status "sh dial-peer voice sum | i voip" will probably show the SIP outbound dial peers as "down"

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎11-14-2019 07:47 PM

Thanks again, I have to find a before config! I'm sure I have a backup somewhere. But here's the output from both show commands:

R2#sh dial-peer voice sum | i voip
21474- voip  up   up             1200               0  syst loopback:rtp
201    voip  up   up             201                0  syst ipv4:192.168.20.4
9      voip  up   up             9[2-9]..[2-9]...-  0  syst sip-server
91     voip  up   up             91[2-9]..[2-9]..-  0  syst sip-server
100    voip  up   up                                0  syst sip-server
911    voip  up   up             911                0  syst sip-server
9911   voip  up   up             9911               0  syst sip-server
202    voip  up   up             202                0  syst ipv4:192.168.20.4
933    voip  up   up             933                0  syst sip-server
9933   voip  up   up             9933               0  syst sip-server

and:

R2#sh sip-ua register status
Line                             peer       expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
1001                             20001      1            no
1002                             20002      0            no
1003                             20003      94           no
300                              300        67           no

and if this can help, that's the content of a SIP packet captured on my WAN interface on my firewall:

Frame 1: 527 bytes on wire (4216 bits), 527 bytes captured (4216 bits)
    Encapsulation type: NULL/Loopback (15)
    Arrival Time: Nov 11, 2019 11:55:33.844055000 Eastern Standard Time
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1573491333.844055000 seconds
    [Time delta from previous captured frame: 0.000000000 seconds]
    [Time delta from previous displayed frame: 0.000000000 seconds]
    [Time since reference or first frame: 0.000000000 seconds]
    Frame Number: 1
    Frame Length: 527 bytes (4216 bits)
    Capture Length: 527 bytes (4216 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: null:ip:udp:sip]
    [Coloring Rule Name: UDP]
    [Coloring Rule String: udp]
Null/Loopback
    Family: IP (2)
Internet Protocol Version 4, Src: 52.52.52.1, Dst: 54.172.60.1
    0100 .... = Version: 4
    .... 0101 = Header Length: 20 bytes (5)
    Differentiated Services Field: 0x68 (DSCP: AF31, ECN: Not-ECT)
    Total Length: 523
    Identification: 0xe0e5 (57573)
    Flags: 0x0000
    Time to live: 253
    Protocol: UDP (17)
    Header checksum: 0x7b51 [validation disabled]
    [Header checksum status: Unverified]
    Source: 52.52.52.1
    Destination: 54.172.60.1
User Datagram Protocol, Src Port: 17630, Dst Port: 5060
    Source Port: 17630
    Destination Port: 5060
    Length: 503
    Checksum: 0x6e1d [unverified]
    [Checksum Status: Unverified]
    [Stream index: 0]
    [Timestamps]
        [Time since first frame: 0.000000000 seconds]
        [Time since previous frame: 0.000000000 seconds]
Session Initiation Protocol (REGISTER)
    Request-Line: REGISTER sip:somedomain.pstn.us1.twilio.com:5060 SIP/2.0
        Method: REGISTER
        Request-URI: sip:somedomain.pstn.us1.twilio.com:5060
            Request-URI Host Part: somedomain.pstn.us1.twilio.com
            Request-URI Host Port: 5060
        [Resent Packet: False]
    Message Header
        Via: SIP/2.0/UDP 100.64.1.2:5060;branch=z9hG4bK1A4C1D88
            Transport: UDP
            Sent-by Address: 100.64.1.2
            Sent-by port: 5060
            Branch: z9hG4bK1A4C1D88
        From: <sip:1002@somedomain.pstn.us1.twilio.com>;tag=1D962544-170F
            SIP from address: sip:1002@somedomain.pstn.us1.twilio.com
                SIP from address User Part: 1002
                SIP from address Host Part: somedomain.pstn.us1.twilio.com
            SIP from tag: 1D962544-170F
        To: <sip:1002@somedomain.pstn.us1.twilio.com>
            SIP to address: sip:1002@somedomain.pstn.us1.twilio.com
                SIP to address User Part: 1002
                SIP to address Host Part: somedomain.pstn.us1.twilio.com
        Date: Mon, 11 Nov 2019 16:55:33 GMT
        Call-ID: E2BA618F-FF6011E9-800481B9-B391AE0B
        [Call-ID: E2BA618F-FF6011E9-800481B9-B391AE0B]
        User-Agent: Cisco-SIPGateway/IOS-12.x
        Max-Forwards: 70
        Timestamp: 1573491333
        CSeq: 1669 REGISTER
            Sequence Number: 1669
            Method: REGISTER
        Contact: <sip:1002@100.64.1.2:5060>
            Contact URI: sip:1002@100.64.1.2:5060
                Contact URI User Part: 1002
                Contact URI Host Part: 100.64.1.2
                Contact URI Host Port: 5060
        Expires: 3600
        Supported: path
        Content-Length: 0

We can see that the payload have an "internal" (100.64.1.2) address and I think it should be my public IP, I have the impression that it's the problem. I see only register SIP packet being sent, but no reponse from Twilio and on Twilio side I don't even see the connection in the log.

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎11-15-2019 02:03 AM

Is 1002 your correct username to register the trunk with Twilio?   Can you also post the full contents of the "sip-ua" section?   I'd expect to see the username defined in a "credentials" line.

I'm also a bit puzzled by the multiple entries in shown in "sip-ua register status".   Are you using SIP phones, it's almost as if they were set to individually register to the provider.

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎11-15-2019 05:56 PM

Hi!

Is 1002 your correct username to register the trunk with Twilio? Can you also post the full contents of the "sip-ua" section? I'd expect to see the username defined in a "credentials" line.

No, 1002 is an extension of one of the phone. It seem like it the sip-ua doesn't even try to authenticate with the provider. Also there's translation rule to change the extension number to an valid ANI number (+4155551212@....) which doesn't seem to happen. here's the sip-ua setting (redacted):

sip-ua
 authentication username bob password 7 [redacted] realm sip.twilio.com
 registrar dns:somedomain.pstn.us1.twilio.com expires 3600
 sip-server dns:somedomain.pstn.us1.twilio.com

Voice translation rules:

voice translation-rule 1
 rule 1 /^91/ /+1/
 rule 2 /^9/ /+1/
!
voice translation-rule 2
 rule 1 /1001/ /2165551212/ !! SCCP Phone 7945
 rule 2 /1002/ /2165551212/ !! SCCP Phone 7941
 rule 3 /300/ /2165551212/ !! Analog card

You can have a look at the config in the original post, perhaps there's something that I overlook. A new set of eyes sometime help!

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎11-16-2019 07:01 AM

You need a "credentials" line under sip-ua with the username (or pilot number) that you want the gateway to use when registering the trunk.  Exactly the same syntax as the "authentication" line that you have.

The voice translation profile won't have any affect on Register messages, it will affect actual calls (or call attempts).

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to o0chrisb0o

‎11-24-2019 01:59 PM - edited ‎11-24-2019 02:01 PM

Hi Tony, sorry for the delay, I had to put this troubleshooting aside, I had other things to do. So I went back to it today. I did check your suggestion to add a credential line in the sip-ua config, I was following the instructions from the provider (https://www.twilio.com/docs/sip-trunking/sample-configuration#cisco). And it did work for the last year and a half before the change.

That being said, I tried something, it did not work, but I think I did a step forward. In the "voice service voip" setting under "sip" I add the following setting "bind control source-interface f0/0.20" and "bind media source-interface f0/0.20" and it change the IPs in the sip message to the IP attach to the interface. So, I tried something, I made a loopback interface with my public IP and changed the source-interface in the bind setting to lo0 instead of f0/0.20, just to see what would happen.

It did not work, but now, in the debug ccsip messages I can see invite message being sent, which wasn't the case before, but no reply. I think it's normal because this command also change the source IP in the header so it get lost on is way back or the firewall drops it on is way out. But when I did this, all incoming call would failed.

I think I need to find a way to change the IP in the sip message

 

Here the sip message after the trick with to Loopback Interface:

Nov 24 21:02:34.538: //22449/78D5ABE78452/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+15148875697@exemple.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 63.20.155.12:5060;branch=z9hG4bK5661201A
Remote-Party-ID: "Paul Carrol" <sip:4155551212@63.20.155.12>;party=calling;screen=no;privacy=off
From: "Paul Carrol" <sip:4155551212@exemple.pstn.us1.twilio.com>;tag=616C5C60-1AE8
To: <sip:+15148875697@exemple.pstn.us1.twilio.com>
Date: Sun, 24 Nov 2019 21:02:34 GMT
Call-ID: 7E61FC22-E3411EA-845781B9-B391AE0B@63.20.155.12
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 2027269095-0238293482-2219999673-3012668939
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1574629354
Contact: <sip:4155551212@63.20.155.12:5060>
Call-Info: <sip:63.20.155.12:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: kpml, telephone-event
Content-Type: application/sdp
Conten
R2#t-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 9537 7548 IN IP4 63.20.155.12
s=SIP Call
c=IN IP4 63.20.155.12
t=0 0
m=audio 19208 RTP/AVP 0 101
c=IN IP4 63.20.155.12
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

The before and after in the config:

before:

voice service voip
 ip address trusted list
  ipv4 100.64.0.0 255.255.255.252
  ipv4 192.168.20.1
  ipv4 100.64.1.0 255.255.255.252
  ipv4 54.172.60.0 255.255.254.0
  ipv4 34.203.250.0 255.255.254.0
  ipv4 54.244.51.0 255.255.255.0
  ipv4 54.171.127.192 255.255.255.192
  ipv4 52.215.127.0 255.255.255.0
  ipv4 35.156.191.128 255.255.255.128
  ipv4 3.122.181.0 255.255.255.0
  ipv4 54.65.63.192 255.255.255.192
  ipv4 3.112.80.0 255.255.255.0
  ipv4 54.169.127.128 255.255.255.192
  ipv4 3.1.77.0 255.255.255.0
  ipv4 54.252.254.64 255.255.255.192
  ipv4 3.104.90.0 255.255.255.0
  ipv4 177.71.206.192 255.255.255.192
  ipv4 18.228.249.0 255.255.255.0
 allow-connections sip to sip
 no supplementary-service sip handle-replaces
 sip
  early-offer forced

After:

voice service voip
 ip address trusted list
  ipv4 100.64.0.0 255.255.255.252
  ipv4 192.168.20.1
  ipv4 100.64.1.0 255.255.255.252
  ipv4 54.172.60.0 255.255.254.0
  ipv4 34.203.250.0 255.255.254.0
  ipv4 54.244.51.0 255.255.255.0
  ipv4 54.171.127.192 255.255.255.192
  ipv4 52.215.127.0 255.255.255.0
  ipv4 35.156.191.128 255.255.255.128
  ipv4 3.122.181.0 255.255.255.0
  ipv4 54.65.63.192 255.255.255.192
  ipv4 3.112.80.0 255.255.255.0
  ipv4 54.169.127.128 255.255.255.192
  ipv4 3.1.77.0 255.255.255.0
  ipv4 54.252.254.64 255.255.255.192
  ipv4 3.104.90.0 255.255.255.0
  ipv4 177.71.206.192 255.255.255.192
  ipv4 18.228.249.0 255.255.255.0
 allow-connections sip to sip
 no supplementary-service sip handle-replaces
 sip
  bind control source-interface FastEthernet0/0.20
  bind media source-interface FastEthernet0/0.20
  registrar server expires max 3600 min 600
  early-offer forced

Let me know if you think of something :)

 

Chris

 

 

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎11-25-2019 01:45 AM

Based on what I've seen with other authenticated trunks, I don't think any sort of Invite is going to work until your sip-ua is registered.   Do you ever seen any outbound Register messages?   If not then maybe the DNS name for the registration server doesn't resolve.

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎11-26-2019 08:25 PM

Hi,

Yes I see outbound register connection, when I did the bind with lo0 interface with my public IP I even seen invite packet go through the WAN with response from Twilio,

I'm starting to explore sip-profile option for outbound dial-peers, my guts tells me that there's something there. What do you think?

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎11-27-2019 12:33 AM

Can you post the debugs for the registration attempts?   "debug ccsip mess" and "debug ccsip non-call" (not all devices need that second one ).   

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎12-07-2019 09:23 AM - edited ‎12-07-2019 09:25 AM

Hi @TONY SMITH ,

here's the output, the command `debug ccsip non-call` isn't available on my system, but I issue `debug ccsip calls` instead:

Dec  7 17:10:29.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:29 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738629
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:31.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:31 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738631
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:35.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:35 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738635
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:36.260: //41585/4508CB1084DD/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+12125551212@mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F8839
Remote-Party-ID: "My Name" <sip:2125551212@192.168.20.1>;party=calling;screen=no;privacy=off
From: "My Name" <sip:2125551212@mydomain.pstn.us1.twilio.com>;tag=A38A5250-17E2
To: <sip:+12125551212@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:36 GMT
Call-ID: 48865DA2-184B11EA-84E281B9-B391AE0B@192.168.20.1
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1158204176-0407572970-2229109177-3012668939
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1575738636
Contact: <sip:2125551212@192.168.20.1:5060>
Call-Info: <sip:192.168.20.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: kpml, telephone-event
Proxy-Authorization: Digest username="user
R2#s",realm="sip.twilio.com",uri="sip:+12125551212@mydomain.pstn.us1.twilio.com:5060",response="513901d52200eac2479b6bd7da9b1c74",nonce="cB5lRvggeCE-uWBVDeB_3AYH8C5Npkyl_2I3foIHNFtZYOId",opaque="eba721d47c10cce3c1a0bdf30248ca9b",cnonce="B3A35832",qop=auth,algorithm=md5,nc=00000001
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 4896 4916 IN IP4 192.168.20.1
s=SIP Call
c=IN IP4 192.168.20.1
t=0 0
m=audio 17982 RTP/AVP 0 101
c=IN IP4 192.168.20.1
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

R2#
Dec  7 17:10:39.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:39 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738639
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:43.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:43 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738643
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:47.928: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:47 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738647
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:48.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:48 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738648
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:49.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:49 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738649
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:51.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:51 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738651
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:52.256: //41585/4508CB1084DD/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+12125551212@mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F8839
Remote-Party-ID: "My Name" <sip:2125551212@192.168.20.1>;party=calling;screen=no;privacy=off
From: "My Name" <sip:2125551212@mydomain.pstn.us1.twilio.com>;tag=A38A5250-17E2
To: <sip:+12125551212@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:52 GMT
Call-ID: 48865DA2-184B11EA-84E281B9-B391AE0B@192.168.20.1
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1158204176-0407572970-2229109177-3012668939
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1575738652
Contact: <sip:2125551212@192.168.20.1:5060>
Call-Info: <sip:192.168.20.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: kpml, telephone-event
Proxy-Authorization: Digest username="user
R2#s",realm="sip.twilio.com",uri="sip:+12125551212@mydomain.pstn.us1.twilio.com:5060",response="513901d52200eac2479b6bd7da9b1c74",nonce="cB5lRvggeCE-uWBVDeB_3AYH8C5Npkyl_2I3foIHNFtZYOId",opaque="eba721d47c10cce3c1a0bdf30248ca9b",cnonce="B3A35832",qop=auth,algorithm=md5,nc=00000001
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 4896 4916 IN IP4 192.168.20.1
s=SIP Call
c=IN IP4 192.168.20.1
t=0 0
m=audio 17982 RTP/AVP 0 101
c=IN IP4 192.168.20.1
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

R2#
Dec  7 17:10:55.244: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:55 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738655
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:55.252: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:55 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738655
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:55.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:55 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738655
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:55.744: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:55 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738655
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:55.752: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:55 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738655
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:56.744: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:56 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738656
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:56.752: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:56 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738656
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:10:58.744: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:58 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738658
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:58.752: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:58 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738658
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:10:59.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:10:59 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738659
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:11:02.744: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:02 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738662
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:02.752: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:02 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738662
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:03.428: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F6267C
From: <sip:1003@mydomain.pstn.us1.twilio.com>;tag=A3898BE4-25FF
To: <sip:1003@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:03 GMT
Call-ID: E2F807B0-FF6011E9-800581B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738663
CSeq: 9314 REGISTER
Contact: <sip:1003@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:11:06.745: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:06 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738666
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:06.753: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:06 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738666
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#
Dec  7 17:11:10.745: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:10 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738670
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:10.753: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#uREGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:10 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738670
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#unde
Dec  7 17:11:14.753: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:14 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738674
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:14.761: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:14 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738674
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:15.249: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:15 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738675
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:15.257: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#undebugREGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:15 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738675
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:16.249: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0F91B6A
From: <sip:user@mydomain.pstn.us1.twilio.com>;tag=A38AD92C-16D
To: <sip:user@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:16 GMT
Call-ID: 45C7AB0C-E4511EA-848781B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738676
CSeq: 3799 REGISTER
Contact: <sip:user@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


Dec  7 17:11:16.257: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

R2#undebug alREGISTER sip:mydomain.pstn.us1.twilio.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.20.1:5060;branch=z9hG4bKA0FA15EC
From: <sip:1001@mydomain.pstn.us1.twilio.com>;tag=A38AD934-126F
To: <sip:1001@mydomain.pstn.us1.twilio.com>
Date: Sat, 07 Dec 2019 17:11:16 GMT
Call-ID: E26C4241-FF6011E9-800381B9-B391AE0B
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1575738676
CSeq: 9317 REGISTER
Contact: <sip:1001@192.168.20.1:5060>
Expires:  3600
Supported: path
Content-Length: 0


R2#ping mydomain.pstn.us1.twilio.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 54.172.60.0, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/20 ms

 

I think the problem might lies within this element in the invite message: "c=IN IP4 192.168.20.1" should it be my public IP? If it's the case, how can I change it? with sip-profile and add a rule to replace it?

Thanks

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to o0chrisb0o

‎12-09-2019 12:51 AM

"here's the output, the command `debug ccsip non-call` isn't available on my system, but I issue `debug ccsip calls` instead:"

That "non-call" debug is platform or maybe version dependent.  On some gateways if you don't include it you don't see SIP Register traffic.

Looking at your debugs you don't have any replies at all.  Personally I think you should concentrate on that aspect at the moment, until the ITSP replies are getting back to you there's no point in worrying about fine tuning other aspects.  Similarly until registration is successful, dial peer configuration is not relevant.

Which interface on the 2811 connects to the 1941?  Just trying to get clear which interface should be transmitting to the ITSP

0 Helpful

Go to solution
o0chrisb0o
Level 1
Level 1
In response to TONY SMITH

‎12-14-2019 09:44 AM - edited ‎12-14-2019 09:48 AM

interface FastEthernet0/2/0 ip address 100.64.1.2 255.255.255.252 connect to the 1941 router.

0 Helpful
Customers Also Viewed These Support Documents