topic Re: Issue with TCL IVR 2.0 Subscribe/Notify on 2431/2921 VGW on IOS 15.1(2)T in Call Control

Issue with TCL IVR 2.0 Subscribe/Notify on 2431/2921 VGW on IOS 15.1(2)T

Alfred Johnson — Thu, 07 May 2015 18:06:49 GMT

Hi,

I am trying to use TCL IVR to get my 2431/2921 VGWs to Subscribe to SIP registration events after successfully Registering with the SIP Proxy on our IMS system. Currently the VGW SIP stack does not support Subscribe/Notify for reg in native IOS code, but the TCL IVR does support a general purpose Subscribe/Notify capability. I wrote a TCL IVR script to do this, but the Subscribe message it sends is being rejected by the IMS, as shown below:

May 7 12:52:20.459 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SUBSCRIBE sip:+18163484000@172.17.253.69:5060 SIP/2.0

Via: SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK66F01AC3

From: sip:+18163484000@ims.eng.rr.com;tag=626AEE7C-154D

To: sip:+18163484000@ims.eng.rr.com

Call-ID: 42C0EA2A-F41011E4-849CDB8F-ECAF76A@10.40.208.29

CSeq: 101 SUBSCRIBE

Max-Forwards: 70

Event: reg

Expires: 1210

Contact: <sip:10.40.208.29:5060>

Content-Length: 0

May 7 12:52:20.471 EDT: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 403 Forbidden - User Not Registered

v:SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK66F01AC3

f:<sip:+18163484000@ims.eng.rr.com>;tag=626AEE7C-154D

t:<sip:+18163484000@ims.eng.rr.com>;tag=1895008750

i:42C0EA2A-F41011E4-849CDB8F-ECAF76A@10.40.208.29

CSeq:101 SUBSCRIBE

l:0

My VGW is actually registered to a somewhat different SIP-URI, before the Subscribe is sent, as shown below.

VGW sip-ua Register From & To SIP-URI: <sip:+18163484000@ims.eng.rr.com>

VGW TCL IVR Request-URI: sip:+18163484000@172.17.253.69:5060

May 7 12:52:51.303 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

Via: SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK66F41259

From: <sip:+18163484000@ims.eng.rr.com>;tag=626B66C0-C9D

To: <sip:+18163484000@ims.eng.rr.com>

Call-ID: 551727A6-F41011E4-849DDB8F-ECAF76A

Max-Forwards: 70

Timestamp: 1431017571

CSeq: 3 REGISTER

Contact: <sip:+18163484000@10.40.208.29:5060>

Expires: 600

Authorization: Digest username="E06F4E57B7BDC175@ims.eng.rr.com",realm="ims.eng.rr.com",uri="sip:ims.eng.rr.com:5060",response="21ad7384c27eb314a5e155099810eca7",nonce="0b31610d554b986311186304b1758c6c174e675f9fdecef68bf347",cnonce="074ED51F",qop=auth,algorithm=md5,nc=00000001

Content-Length: 0

May 7 12:52:51.363 EDT: //14200/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

v:SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK66F41259

f:<sip:+18163484000@ims.eng.rr.com>;tag=626B66C0-C9D

t:<sip:+18163484000@ims.eng.rr.com>;tag=1185677959

i:551727A6-F41011E4-849DDB8F-ECAF76A

CSeq:3 REGISTER

m:<sip:+18163484000@10.40.208.29:5060>;audio;expires=600

Path:<sip:cakpcscf.ims.eng.rr.com:5070;lr>

Service-Route:<sip:originating@abrscscf.ims.eng.rr.com:5090;reg-id=111431017571333507;lskpmc=S11;lr;ms_rest_id=S11554b9863>

P-com.siemens.maximum-chat-size:1300

P-com.siemens.maximum-IM-size:1300

P-com.siemens.chat:direct

P-Associated-URI:<sip:+18163484000@ims.eng.rr.com>

P-Associated-URI:<sip:+18163484001@ims.eng.rr.com;end-num=18163484999>

l:0

Further below is my complete TCL IVR script, but the problem seems to be in the following TCL command that invokes the Subscribe:

subscription open sip:+18163484000@ims.eng.rr.com SubscrParams

For some reason, the subscription open command decides to do a dns query to resolve the host part of the URL parameter in the open, ims.eng.rr.com, and put the resulting IP address in the Subscribe Request-URI,

I have an example of a Subscribe message that is accepted by IMS, from another platform we use shown below. You can see that its Request URI does not contain a resolved IP address, but puts the literal SIP Realm domain name for the host part.

SUBSCRIBE sip:+18163225773@ims.eng.rr.com;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.40.209.14:5060;branch=z9hG4bK-d8754z-6c19cd6b20f27144-1---d8754z-;rport

Max-Forwards: 70

Route: <sip:eepcscf-gm.ims.eng.rr.com;lr>

Contact: <sip:+18163225773@10.40.209.14:5060;user=phone>

To: "Doscis SIP"<sip:+18163225773@ims.eng.rr.com;user=phone>

From: "Doscis SIP"<sip:+18163225773@ims.eng.rr.com;user=phone>;tag=3879f398

Call-ID: NzE0YjY2NGU2ZDdjN2I4OGQ0ZjRmNWE0MmVkZDM2Njk.

CSeq: 2 SUBSCRIBE

Expires: 1210

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

Proxy-Authorization: Digest username="192BAC9531407265@ims.eng.rr.com",realm="ims.eng.rr.com",nonce="09c1a75f50cbb0471350477bc4b045cd697e3097e8c85e6a14bbca",uri="sip:+18163225773@ims.eng.rr.com;user=phone",response="59d250ba43cb7866fef04c85c20a8890",cnonce="af43a5e3373f5c52",nc=00000001,qop=auth,algorithm=MD5

Supported: timer

User-Agent: ESBC9328-4B-2.0.12.40-Build3

Event: reg

Content-Length: 0

SIP/2.0 200 OK

v:SIP/2.0/UDP 10.40.209.14:5060;branch=z9hG4bK-d8754z-6c19cd6b20f27144-1---d8754z-;rport=5060;received=10.40.209.14

t:"Doscis SIP"<sip:+18163225773@ims.eng.rr.com;user=phone>;tag=2145026813

f:"Doscis SIP"<sip:+18163225773@ims.eng.rr.com;user=phone>;tag=3879f398

i:NzE0YjY2NGU2ZDdjN2I4OGQ0ZjRmNWE0MmVkZDM2Njk.

CSeq:2 SUBSCRIBE

Expires:1210

m:<sip:rdceescscf2.ims.eng.rr.com:5090;lskpmc=S35>

Record-Route:<sip:172.17.254.170;routing_id=pcscf_a_side;lskpmc=P19;lr;serv_user=10.40.209.14:5060>

l:0

So I am wondering if anybody knows how I can do to get the TCL IVR subscription open command to use the literal SIP realm domain name instead of the resolved IP address in the Subscribe's Request-URI. I would certainly appreciate any help anyone can offer. Below is the full TCL script, followed by the brief IOS application config statements that invoke it..

Alfy Johnson

Time Warner Cable, Herndon Virginia

bctrunks-2431-4#show call application voice SubscribeReg

Script Name : SubscribeReg

URL : flash:SubscribeReg.tcl

Type : Service

State: Registered

Life : Configured

Exec Instances: 1

Parameters registered under SubscribeReg namespace:

name type default value description

uid-len I 10 the number of digits in UID

warning-time I 30 the time (in secs) within which a user is warned before the calling time expires (call terminates)

pin-len I 4 the number of digits in PIN

retry-count I 3 the number of attempts to reenter PIN

redirect-number S the telephone number where a call is redirected to

Script Code Begin:

--------------------------------

TCL Script version 2.0 - 2.1

# SubscribeReg.tcl

#------------------------------------------------------------------

# Script Version 0.1 - 2015-5-5

# This tcl script

#------------------------------------------------------------------

proc init { } {

global param

}

proc Send_Subscribe { } {

# not working set headers(User-Agent) "Cisco 2431 15.1 TCL IVR 2.0"

set headers(From) "sip:+18163484000@ims.eng.rr.com"

set headers(To) "sip:+18163484000@ims.eng.rr.com"

set SubscrParams(protoHeaders) headers

set SubscrParams(event) reg

set SubscrParams(expirationTime) 1210

set mySubID [subscription open sip:+18163484000@ims.eng.rr.com SubscrParams]

}

proc Check_Response { } {

set status [infotag get evt_status]

puts status

if { $status != "su_000"} {

puts "Successful Subscribe"

}

proc Timeout { } {

puts "Expires Timer Expired"

}

proc act_Abort { } {

puts "Unexpected event - entering act_Abort"

call close

}

init

#----------------------------------

# State Machine

#----------------------------------

set SubscribeSM(any_state,ev_disconnected) "act_Abort,same_state"

set SubscribeSM(SUBSCRIBING,ev_any_event) "Send_Subscribe,WAIT_FOR_RESPONSE"

set SubscribeSM(WAIT_FOR_RESPONSE,ev_subscribe_done) "Check_Response,NORMAL"

set SubscribeSM(NORMAL,ev_unsubscribe_indication) "Timeout,SUBSCRIBING"

fsm define SubscribeSM SUBSCRIBING

--------------------------------

bctrunks-2431-4#srs application

application

service SubscribeReg flash:SubscribeReg.tcl

monitor

interface stats

interface event-log

interface event-log flash

stats

event-log

bctrunks-2431-4#ssrs

Line peer expires(sec) registered P-Associ-URI

================================ ========== ============ ========== ============

+18163484000 -1 162 yes +18163484000

+18163484001

Re: Issue with TCL IVR 2.0 Subscribe/Notify on 2431/2921 VGW on IOS 15.1(2)T

yawming — Thu, 07 May 2015 20:10:21 GMT

Tcl IVR is an application framework based on IOS. If IOS doesn't have such feature I doubt the Tcl script will work on top of that IOS

Re: Issue with TCL IVR 2.0 Subscribe/Notify on 2431/2921 VGW on IOS 15.1(2)T

Alfred Johnson — Thu, 07 May 2015 20:33:07 GMT

The SIP Subscribe/Notify feature is documented in the IOS 15.1 SIP Config guide, and int the TCL IVR Applications Guide for IOS, so yes IOS does support it. You just set the event value to "reg" which makes it work for SIP registration events.

Re: Issue with TCL IVR 2.0 Subscribe/Notify on 2431/2921 VGW on IOS 15.1(2)T

Alfred Johnson — Fri, 08 May 2015 14:21:26 GMT

I was able to get the Subscribe to work using the voice class sip-profiles command to modify the outgoing Subscribe message:

bctrunks-2431-4#srs voice class sip-profiles

voice class sip-profiles 100

. . .

request SUBSCRIBE sip-header SIP-Req-URI modify "(.*)@.*" "\1@ims.eng.rr.com;user=phone SIP/2.0"

Below is the output of debug ccsip messages:

May 8 09:41:03.228 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SUBSCRIBE sip:+18163484000@ims.eng.rr.com;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK68411986

From: sip:+18163484000@ims.eng.rr.com;tag=66E22814-DA5

To: sip:+18163484000@ims.eng.rr.com

Call-ID: B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

CSeq: 101 SUBSCRIBE

Max-Forwards: 70

Event: reg

Expires: 1210

Contact: <sip:10.40.208.29:5060>

Content-Length: 0

May 8 09:41:03.244 EDT: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 407 Proxy Authentication Required

v:SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK68411986

f:<sip:+18163484000@ims.eng.rr.com>;tag=66E22814-DA5

t:<sip:+18163484000@ims.eng.rr.com>;tag=986239153

i:B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

CSeq:101 SUBSCRIBE

Proxy-Authenticate:Digest realm="ims.eng.rr.com",nonce="75dddaec554cbcef111cef05ea5c403a2123215769b1379d4fb37d",qop="auth"

l:0

May 8 09:41:03.248 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SUBSCRIBE sip:+18163484000@ims.eng.rr.com;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK68421E92

From: sip:+18163484000@ims.eng.rr.com;tag=66E22814-DA5

To: sip:+18163484000@ims.eng.rr.com

Call-ID: B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

Max-Forwards: 70

Event: reg

Expires: 1210

Contact: <sip:10.40.208.29:5060>

Content-Length: 0

Proxy-Authorization: Digest username="E06F4E57B7BDC175@ims.eng.rr.com",realm="ims.eng.rr.com",uri="sip:+18163484000@172.17.254.75:5060",response="5449f4c2ca85270b40eab3e6b97600ae",nonce="75dddaec554cbcef111cef05ea5c403a2123215769b1379d4fb37d",cnonce="1F86A2C9",qop=auth,algorithm=md5,nc=00000001

CSeq: 102 SUBSCRIBE

May 8 09:41:03.272 EDT: //0/000000000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

v:SIP/2.0/UDP 10.40.208.29:5060;branch=z9hG4bK68421E92

f:<sip:+18163484000@ims.eng.rr.com>;tag=66E22814-DA5

t:<sip:+18163484000@ims.eng.rr.com>;tag=1254025593

i:B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

CSeq:102 SUBSCRIBE

Expires:1210

m:<sip:abrscscf.ims.eng.rr.com:5090;lskpmc=S11>

Record-Route:<sip:172.17.254.170;routing_id=pcscf_a_side;lskpmc=P11;lr;serv_user=10.40.208.29:5060>

l:0

May 8 09:41:03.276 EDT: //-1//AFW_:EE6791A580000:/AFW_M_TclModule_Action:

May 8 09:41:03.276 EDT: //-1//AFW_:EE6791A580000:/AFW_TclModule_DefaultEvHandling:

May 8 09:41:03.280 EDT: //-1//TCL :EE6791A580000:/tcl_InfotagObjCmd: infotag get evt_status

May 8 09:41:03.280 EDT: //-1//TCL :EE6791A580000:/tcl_InfotagGetObjCmd: infotag get evt_status

May 8 09:41:03.280 EDT: //-1//AFW_:EE6791A580000:/vtr_ev_status: argc 2 argindex 2

May 8 09:41:03.280 EDT: //-1//TCL :EE6791A580000:/tcl_PutsObjCmd: status

May 8 09:41:03.280 EDT:

May 8 09:41:03.288 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:10.40.208.29:5060 SIP/2.0

v:SIP/2.0/TCP 172.17.254.170:5060;branch=z9hG4bKc96ca3c2c2e7da83fb9759288d008de5;lskpmc=P11

Record-Route:<sip:172.17.254.170;routing_id=pcscf_a_side;lskpmc=P11;lr>

v:SIP/2.0/TCP 172.17.254.75:5090;branch=z9hG4bK93a8447a0d8890d6e32d6205611029d1;lskpmc=S11

f:<sip:+18163484000@ims.eng.rr.com>;tag=1254025593

t:<sip:+18163484000@ims.eng.rr.com>;tag=66E22814-DA5

o:reg

i:B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

Subscription-State:active

CSeq:1 NOTIFY

c:application/reginfo+xml

m:<sip:abrscscf.ims.eng.rr.com:5090;lskpmc=S11>

Max-Forwards:68

l:705

<?xml version="1.0"?><reginfo xmlns="urn:ietf:params:xml:ns:reginfo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0" state="full"><registration aor="sip:+18163484000@ims.eng.rr.com" id="7d94aa39111431092326854924" state="active"><contact id="111431092326854924" state="active" event="registered"><uri>sip:+18163484000@10.40.208.29:5060</uri><unknown-param name="audio"/></contact></registration><registration aor="sip:+18163484001@ims.eng.rr.com;end-num=18163484999" id="a9968911111431092326854924" state="active"><contact id="111431092326854924" state="active" event="created"><uri>sip:+18163484000@10.40.208.29:5060</uri><unknown-param name="audio"/></contact></registration></reginfo>

May 8 09:41:03.296 EDT: //-1//AFW_:EE6791A580000:/AFW_M_TclModule_Action:

May 8 09:41:03.296 EDT: //-1//AFW_:EE6791A580000:/AFW_TclModule_DefaultEvHandling:

May 8 09:41:03.296 EDT: //-1//AFW_:EE6791A580000:/AFW_FSM_Drive: FSM no match for (NORMAL[2],ev_notify_indication[193])

May 8 09:41:08.296 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/TCP 172.17.254.170:5060;branch=z9hG4bKc96ca3c2c2e7da83fb9759288d008de5;lskpmc=P11,SIP/2.0/TCP 172.17.254.75:5090;branch=z9hG4bK93a8447a0d8890d6e32d6205611029d1;lskpmc=S11

From: sip:+18163484000@ims.eng.rr.com;tag=1254025593

To: sip:+18163484000@ims.eng.rr.com;tag=66E22814-DA5

Date: Fri, 08 May 2015 13:41:08 GMT

Call-ID: B4343033-F4BE11E4-84A6DB8F-ECAF76A@10.40.208.29

CSeq: 1 NOTIFY

Record-Route: <sip:172.17.254.170;routing_id=pcscf_a_side;lskpmc=P11;lr>

Content-Length: 0