Testing e-933 on Vitelity - how to configure

I ordered my e-911 service on Vitelity several weeks ago and finally had a chance to test it out.
I have my 911/933 outbound route first in the route order.
My vitelity inbound did and outbound calls work perfectly. My e-911 service is active in the Vitelity portal.
My calls to 933 fail.
Is there a special Prepend I need to add in the outbound route or trunk to complete the 933 call?
I’ve tried forcing caller ID in the second example, but still not working.

– Executing [[email protected]:31] Dial(“SIP/112-00000014”, “SIP/vitel-outbound/933,300,Tb(func-apply-sipheaders^s^1)”) in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
– SIP/vitel-outbound-00000015 Internal Gosub(func-apply-sipheaders,s,1) start
– Executing [[email protected]:1] ExecIf(“SIP/vitel-outbound-00000015”, “0?Set(CHANNEL(hangup_handler_push)=crm-hangup,s,1)”) in new stack
– Executing [[email protected]:2] NoOp(“SIP/vitel-outbound-00000015”, “Applying SIP Headers to channel”) in new stack
– Executing [[email protected]:3] Set(“SIP/vitel-outbound-00000015”, “SIPHEADERKEYS=”) in new stack
– Executing [[email protected]:4] While(“SIP/vitel-outbound-00000015”, “0”) in new stack
– Jumping to priority 8
– Executing [[email protected]:9] Return(“SIP/vitel-outbound-00000015”, “”) in new stack
== Spawn extension (from-trunk, 933, 1) exited non-zero on ‘SIP/vitel-outbound-00000015’
– SIP/vitel-outbound-00000015 Internal Gosub(func-apply-sipheaders,s,1) complete GOSUB_RETVAL=
– Called SIP/vitel-outbound/933
– Got SIP response 484 “Address Incomplete” back from 64.2.142.189:5060
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [[email protected]:32] NoOp(“SIP/112-00000014”, “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 28”) in new stack
– Executing [[email protected]:33] GotoIf(“SIP/112-00000014”, “0?continue,1:s-CHANUNAVAIL,1”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
– Executing [[email protected]:1] Set(“SIP/112-00000014”, “RC=28”) in new stack
– Executing [[email protected]:2] Goto(“SIP/112-00000014”, “28,1”) in new stack
– Goto (macro-dialout-trunk,28,1)
– Executing [[email protected]:1] Goto(“SIP/112-00000014”, “s-INVALIDNMBR,1”) in new stack
– Goto (macro-dialout-trunk,s-INVALIDNMBR,1)


Forcing my callerid to be vitelity did

– Executing [[email protected]:29] ExecIf(“SIP/112-0000001e”, “0?Set(CONNECTEDLINE(name,i)=CID:(Hidden)7577078333)”) in new stack
– Executing [[email protected]:30] GotoIf(“SIP/112-0000001e”, “0?customtrunk”) in new stack
– Executing [[email protected]:31] Dial(“SIP/112-0000001e”, “SIP/vitel-outbound/933,300,Tb(func-apply-sipheaders^s^1)”) in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
– SIP/vitel-outbound-0000001f Internal Gosub(func-apply-sipheaders,s,1) start
– Executing [[email protected]:1] ExecIf(“SIP/vitel-outbound-0000001f”, “0?Set(CHANNEL(hangup_handler_push)=crm-hangup,s,1)”) in new stack
– Executing [[email protected]:2] NoOp(“SIP/vitel-outbound-0000001f”, “Applying SIP Headers to channel”) in new stack
– Executing [[email protected]:3] Set(“SIP/vitel-outbound-0000001f”, “SIPHEADERKEYS=”) in new stack
– Executing [[email protected]:4] While(“SIP/vitel-outbound-0000001f”, “0”) in new stack
– Jumping to priority 8
– Executing [[email protected]:9] Return(“SIP/vitel-outbound-0000001f”, “”) in new stack
== Spawn extension (from-trunk, 933, 1) exited non-zero on ‘SIP/vitel-outbound-0000001f’
– SIP/vitel-outbound-0000001f Internal Gosub(func-apply-sipheaders,s,1) complete GOSUB_RETVAL=
– Called SIP/vitel-outbound/933
– Got SIP response 484 “Address Incomplete” back from 64.2.142.189:5060
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [[email protected]:32] NoOp(“SIP/112-0000001e”, “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 28”) in new stack
– Executing [[email protected]:33] GotoIf(“SIP/112-0000001e”, “0?continue,1:s-CHANUNAVAIL,1”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
– Executing [[email protected]:1] Set(“SIP/112-0000001e”, “RC=28”) in new stack
– Executing [[email protected]:2] Goto(“SIP/112-0000001e”, “28,1”) in new stack
– Goto (macro-dialout-trunk,28,1)
– Executing [[email protected]:1] Goto(“SIP/112-0000001e”, “s-INVALIDNMBR,1”) in new stack
– Goto (macro-dialout-trunk,s-INVALIDNMBR,1)
– Executing [[email protected]:1] NoOp(“SIP/112-0000001e”, “Dial failed due to trunk reporting Address Incomplete - giving up”) in new stack
– Executing [[email protected]:2] Progress(“SIP/112-0000001e”, “”) in new stack
– Executing [[email protected]:3] Playback(“SIP/112-0000001e”, “ss-noservice,noanswer”) in new stack
– <SIP/112-0000001e> Playing ‘ss-noservice.ulaw’ (language ‘en’)

0x7fbfac07bc00 – Strict RTP switching to RTP target address 192.168.0.198:58726 as source
0x7fbfac07bc00 – Strict RTP learning complete - Locking on source address 192.168.0.198:58726
– Executing [[email protected]:1] Hangup(“SIP/112-0000001e”, “”) in new stack
== Spawn extension (restrictedroute-453e406dcee4d18174d4ff623f52dcd8, h, 1) exited non-zero on ‘SIP/112-0000001e’
– SIP/112-0000001e Internal Gosub(crm-hangup,s,1) start
– Executing [[email protected]:1] NoOp(“SIP/112-0000001e”, “Sending Hangup to CRM”) in new stack
– Executing [[email protected]:2] NoOp(“SIP/112-0000001e”, “HANGUP CAUSE: 28”) in new stack
– Executing [[email protected]:3] ExecIf(“SIP/112-0000001e”, “0?Set(__CRM_VOICEMAIL=)”) in new stack
– Executing [[email protected]:4] NoOp(“SIP/112-0000001e”, "MASTER CHANNEL:

Is 933 supposed to be the Vitelity test number that announces your CallerID?

I am also using Vitelity and in my case it’s 811.

1 Like

Nuts.

Thank you. It works!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.