TELUS OneVoice SIP settings 1

[salert]

Hi All,
Having an issue with a new sip provider (TELUS OneVoice) they have different requirements that I'm used to tracing out the call I have a 503 error. One of the requirements I seen was to have the user=phone in the from message anyone know the setting to get this?


INVITE sip:+19088485606@192.168.1.9;user=phone SIP/2.0

From: "T-SIP-9611" <sip:+15872330333@17.18.19.228:5060;user=phone>;tag=80c24a1ec60e417b735456ff400

 

[janni78]

You can set it on the Advanced tab on the SIP line.

"Trying is the first step to failure..." - Homer

 

[salert]

Thanks janni78 unfortunately once I added it, it still didn't work looks like my invite is failing here is a screen shot I don't really see why it's failing....

15:22:44 823413mS SIP Call Tx: 10
INVITE sip:+15878767711@38.140.220.107;user=phone SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.1.9.0 build 182
P-Asserted-Identity: "TELUS" <sip:+15876210806@64.56.137.137:5060>
Content-Type: application/sdp
Content-Length: 252

v=0
o=UserA 1476510922 209987374 IN IP4 64.56.137.137
s=Session SDP
c=IN IP4 64.56.137.137
t=0 0
m=audio 10000 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:22:44 823413mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
INVITE sip:+15878767711@38.140.220.107;user=phone SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 9.1.9.0 build 182
P-Asserted-Identity: "TELUS" <sip:+15876210806@64.56.137.137:5060>
Content-Type: application/sdp
Content-Length: 252

v=0
o=UserA 1476510922 209987374 IN IP4 64.56.137.137
s=Session SDP
c=IN IP4 64.56.137.137
t=0 0
m=audio 10000 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:22:44 823516mS SIP Rx: UDP 38.140.220.107:5060 -> 192.168.88.250:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 64.56.137.137:5060;received=64.56.137.137;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89;rport=5060
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE

15:22:44 823517mS Sip: Find End Point2 c0a858fa00000400 10.1024.0 7 SIPTrunk Endpoint (f4fb4dec) Sip CallId e25fae1b5eb2f6198c81719418a29278
15:22:44 823518mS SIP Call Rx: 10
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 64.56.137.137:5060;received=64.56.137.137;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89;rport=5060
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE

15:22:44 823520mS SIP Rx: UDP 38.140.220.107:5060 -> 192.168.88.250:5060
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 64.56.137.137:5060;received=64.56.137.137;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89;rport=5060
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>;tag=aprqngfrt-a753tek67fccb
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE

15:22:44 823522mS Sip: Find End Point2 c0a858fa00000400 10.1024.0 7 SIPTrunk Endpoint (f4fb4dec) Sip CallId e25fae1b5eb2f6198c81719418a29278
15:22:44 823522mS SIP Call Rx: 10
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 64.56.137.137:5060;received=64.56.137.137;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89;rport=5060
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>;tag=aprqngfrt-a753tek67fccb
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 INVITE

15:22:44 823525mS SIP Call Tx: 10
ACK sip:+15878767711@38.140.220.107;user=phone SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>;tag=aprqngfrt-a753tek67fccb
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 ACK
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
User-Agent: IP Office 9.1.9.0 build 182
Content-Length: 0

15:22:44 823525mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
ACK sip:+15878767711@38.140.220.107;user=phone SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK7bf1df7cd4023bfeceda957080253c89
From: "TELUS" <sip:+15876210806@38.140.220.107;user=phone>;tag=43fbe7fcb30e0596
To: <sip:+15878767711@38.140.220.107;user=phone>;tag=aprqngfrt-a753tek67fccb
Call-ID: e25fae1b5eb2f6198c81719418a29278
CSeq: 904343990 ACK
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
User-Agent: IP Office 9.1.9.0 build 182
Content-Length: 0

15:22:49 828526mS Sip: Timer 4 callback didn't find dialog, method ACK, callid e25fae1b5eb2f6198c81719418a29278

 

[derfloh]

The provider has to tell you what they expect to see in which header field.

Perhaps a comparison with an inbound call can give you more insight.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[bahmonkeys]

To resolve this you need to remove the user=phone from the header. Have you got an SBC? I have a string that can remove this from the header but can only be applied to an SBC. I have a seen this removed from the Sip trunk engineering custom string tab but you may have to ask Avaya for this string. Or contact the Sip Provider and ask them to remove this from the header.

 

[salert]

Hi derfloh they have it's the following I thought I believe it looks like what the requested:

3. Outbound Caller ID and P-Asserted-Identity Header
When calling outbound from your IP Trunking service, calls are routed and billed based on the
“P-Asserted-Identity” header in the SIP INVITE message, and not the “From” header. PAI is a required
header in the TELUS network and must be sent in the SIP URI format, for example:
P-Asserted-Identity: "TELUS"<sip:+16045555555@10.10.10.1;user=phone>
SIP Display info: "TELUS"
SIP PAI Address: sip:+16045555555@10.10.10.1;user=phone
SIP PAI User Part: 6045555555
SIP PAI Host Part: 10.10.10.1
SIP PAI URI parameter: user=phone
The SIP PAI User Part must be a valid DID that has been assigned to your One Voice SIP Trunking service
and the PAI Host Part is generally the external IP address of your SBC. TELUS One Voice supports GNF, i.e.
E.164, so please ensure to include the “+” sign in the number.
For outbound caller ID, the “From” header in the SIP INVITE is used and it can be any phone number that
you would like to have displayed such as a toll-free number. The number does not have to be one of your IP
Trunking DIDs.

Here is a successful inbound call:
15:14:53 353376mS SIP Rx: UDP 38.140.220.107:5060 -> 192.168.88.250:5060
INVITE sip:+15876210806@64.56.137.137:5060 SIP/2.0
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care"<sip:4038877741@38.140.220.107:5060>;tag=48610
To: "5876210806"<sip:+15876210806@64.56.137.137:5060;user=phone>
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Content-Type: application/sdp
Contact: <sip:38.140.220.107:5060;transport=udp>
User-Agent: Nortel SESM 19.0.3.1
Max-Forwards: 18
Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin,com.nortelnetworks.im.encryption,replaces,tdialog,100rel
Allow: INVITE,BYE,CANCEL,ACK,REGISTER,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,INFO,REFER,OPTIONS,PUBLISH,PRACK
Content-Length: 224

v=0
o=- 2779512921 1341170655 IN IP4 209.91.94.6
s=-
p=+1 6135555555
c=IN IP4 38.140.220.107
t=0 0
m=audio 64646 RTP/AVP 0 101 18
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=ptime:20
15:14:53 353380mS SIP Call Rx: 10
INVITE sip:+15876210806@64.56.137.137:5060 SIP/2.0
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care"<sip:4038877741@38.140.220.107:5060>;tag=48610
To: "5876210806"<sip:+15876210806@64.56.137.137:5060;user=phone>
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Content-Type: application/sdp
Contact: <sip:38.140.220.107:5060;transport=udp>
User-Agent: Nortel SESM 19.0.3.1
Max-Forwards: 18
Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin,com.nortelnetworks.im.encryption,replaces,tdialog,100rel
Allow: INVITE,BYE,CANCEL,ACK,REGISTER,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,INFO,REFER,OPTIONS,PUBLISH,PRACK
Content-Length: 224

v=0
o=- 2779512921 1341170655 IN IP4 209.91.94.6
s=-
p=+1 6135555555
c=IN IP4 38.140.220.107
t=0 0
m=audio 64646 RTP/AVP 0 101 18
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=ptime:20
15:14:53 353386mS SIP Call Tx: 10
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Length: 0

15:14:53 353386mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Length: 0

15:14:53 353407mS SIP Call Tx: 10
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Length: 0

15:14:53 353407mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Length: 0

15:14:56 355450mS SIP Call Tx: 10
SIP/2.0 200 OK
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Type: application/sdp
Content-Length: 206

v=0
o=UserA 1956940965 2700418944 IN IP4 64.56.137.137
s=Session SDP
c=IN IP4 64.56.137.137
t=0 0
m=audio 10000 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:14:56 355450mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bKhppd9j00586h9nd0g1c0.2
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 INVITE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.1.9.0 build 182
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Content-Type: application/sdp
Content-Length: 206

v=0
o=UserA 1956940965 2700418944 IN IP4 64.56.137.137
s=Session SDP
c=IN IP4 64.56.137.137
t=0 0
m=audio 10000 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
15:14:56 355640mS SIP Rx: UDP 38.140.220.107:5060 -> 192.168.88.250:5060
ACK sip:+15876210806@64.56.137.137:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bK4ju0780090chnm9s63h0.1
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 ACK
Contact: <sip:38.140.220.107:5060;transport=udp>
User-Agent: Nortel SESM 19.0.3.1
Max-Forwards: 18
Content-Length: 0

15:14:56 355642mS Sip: Find End Point2 c0a858fa000003f6 10.1014.1 5 SIPTrunk Endpoint (f4fb4dec) Sip CallId 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
15:14:56 355642mS SIP Call Rx: 10
ACK sip:+15876210806@64.56.137.137:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 38.140.220.107:5060;branch=z9hG4bK4ju0780090chnm9s63h0.1
From: "Bethany Care" <sip:4038877741@38.140.220.107:5060>;tag=48610
To: "5876210806" <sip:+15876210806@64.56.137.137:5060;user=phone>;tag=0c9a2fb21f1da92f
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58699 ACK
Contact: <sip:38.140.220.107:5060;transport=udp>
User-Agent: Nortel SESM 19.0.3.1
Max-Forwards: 18
Content-Length: 0

15:14:57 356978mS SIP Call Tx: 10
BYE sip:38.140.220.107:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK6db844e1f7325ae97ddea51316742235
From: "5876210806" <sip:+15876210806@64.56.137.137;user=phone>;tag=0c9a2fb21f1da92f
To: "Bethany Care" <sip:4038877741@38.140.220.107>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58700 BYE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Reason: Q.850;cause=16;text="Normal call clearing"
User-Agent: IP Office 9.1.9.0 build 182
Content-Length: 0

15:14:57 356979mS SIP Tx: UDP 192.168.88.250:5060 -> 38.140.220.107:5060
BYE sip:38.140.220.107:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 64.56.137.137:5060;rport;branch=z9hG4bK6db844e1f7325ae97ddea51316742235
From: "5876210806" <sip:+15876210806@64.56.137.137;user=phone>;tag=0c9a2fb21f1da92f
To: "Bethany Care" <sip:4038877741@38.140.220.107>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58700 BYE
Contact: "TELUS" <sip:+15876210806@64.56.137.137:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Reason: Q.850;cause=16;text="Normal call clearing"
User-Agent: IP Office 9.1.9.0 build 182
Content-Length: 0

15:14:58 357164mS SIP Rx: UDP 38.140.220.107:5060 -> 192.168.88.250:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 64.56.137.137:5060;received=64.56.137.137;branch=z9hG4bK6db844e1f7325ae97ddea51316742235;rport=5060
From: "5876210806" <sip:+15876210806@64.56.137.137;user=phone>;tag=0c9a2fb21f1da92f
To: "Bethany Care" <sip:4038877741@38.140.220.107>;tag=48610
Call-ID: 6d4eb21c075a2694842e6945f8a0adfe2c9bc84b@100.64.31.39
CSeq: 58700 BYE
Content-Length: 0

 

[salert]

bahmonkeys it looks like that is a requirement I can easily remove that in advanced setting. Thanks.

 

[janni78]

Seems odd that they want CLI in E.164 format but themselves send it with +1.
From the looks of it, it seems to be correct so easiest would be if the service provider can answer what is wrong.

They also answer Service Unavailable which could be anything from configuration error to one of their servers being down.
Normally you would just get Forbidden and a reason why.

"Trying is the first step to failure..." - Homer

 

[derfloh]

I agree with janni. It looks good and they have to tell you what's wrong.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN