SIP Trunk registration issue TELUS

[salert]

Hi we have taken over a new customer which has these TELUS SIP trunks (Ring Central) successfully registered on a grandstream device switching to an IP Office 500v2 rel 12.0. Under the SIP line the ITSP Domain name we get the following warning: We can change the name to anything else and it accepts have changed to the actual IP address and it accepts but still can't get the SIP Trunk registered. Has anyone seen this warning before, can the IP office actually have this domain name blocked?

 

[derfloh]

Seems to be blocked to not link IPO to Ringcentral

 

[Menniss]

Well this is a bit cheeky of them. I had a look and can load this on a R11.0 system without the error. Got the error on a R11.1 system. I loaded it with just the IP address.

I can see it sending the registration request but there is no reply.

Could be anything but if they went to the trouble of codding to block the use of sip.ringcentral.com then wouldn't surprise, me if they did something at the ring central end to block it.

You will need to contact TELUS I think

 

[derfloh]

I’m not familiar with ACO/RingCentral. But maybe the sell another license to allow the connection.

 

[salert]

Great thanks Menniss that's very interesting it's allowing you on 11.0. I did get a reply when I did an ns lookup and put in the public IP address. Below is my trace:

8594159mS Sip: SIP Line (18) RestartTrunkComm now 1 dns 0 from_trunk_in_service 0
8594160mS Sip: SIP Line (18): StartTrunkComm enabled 1 in_service 0 from_startup 0
8594160mS Sip: SIP Line (18): StartTrunkComm dns_ok 1 OptionsNeededForKeepAlive 0 RequiresRegistration 1 check_oos 1
8594161mS Sip: SIP Line (18) SetTrunkInService 0 (previous: 0, from_reg: 0, response code: 0 from_stop_trunk 0) begin checks...
8602370mS Sip: SIP Line (18) proxy_usage[0].options_supported = 1 (SelectProxyIPAddr)
8602371mS Sip: SIP Line (18): sip_trunk_config_items 50020001, sip_trunk_config_items_2 00000000, voip.flags 00000948
8602371mS Sip: SIPDialog f4f98ac8 created, dialogs 6 txn_keys 0 video 0 presentation 0 camera 0 unsupp audio 0
8602372mS Sip: 0000000000000000 0.805307506.0 -1 SIPTrunk Endpoint(f4f98ac8) SetUnIntTransactionCondition to UnInt_None
8602373mS Sip: c0a8030a30000472 0.805307506.0 -1 SIPTrunk Endpoint(f4f98ac8) REGISTER SENT TO 199.255.120.176 5090
8602374mS SIP Reg/Opt Tx: 18
REGISTER sip:199.255.120.146 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.10:5060;rport;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
Contact: <sip:15878024935@192.168.3.10:5060;transport=udp>
Expires: 3600
Authorization: Digest username="414828050",realm="10.13.120.93",nonce="Z1t7F2dbeev5rHqM+N/FphRLC4ORkRB/",response="8e5e3fc5c52e18bb641754f17887cd6b",uri="sip:199.255.120.146"
Max-Forwards: 70
User-Agent: IP Office 12.0.0.0.0 build 56
Supported: timer
Content-Length: 0

8602376mS SIP Tx: UDP 192.168.3.10:5060 -> 199.255.120.176:5090
REGISTER sip:199.255.120.146 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.10:5060;rport;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
Contact: <sip:15878024935@192.168.3.10:5060;transport=udp>
Expires: 3600
Authorization: Digest username="414828050",realm="10.13.120.93",nonce="Z1t7F2dbeev5rHqM+N/FphRLC4ORkRB/",response="8e5e3fc5c52e18bb641754f17887cd6b",uri="sip:199.255.120.146"
Max-Forwards: 70
User-Agent: IP Office 12.0.0.0.0 build 56
Supported: timer
Content-Length: 0

8602420mS SIP Rx: UDP 199.255.120.176:5090 -> 192.168.3.10:5060
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 192.168.3.10:5060;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867;rport=1026
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
Server: kamailio (5.7.5 (x86_64/linux))
Content-Length: 0

8602422mS Sip: Find End Point c0a8030a30000472 0.805307506.0 -1 SIPTrunk Endpoint (f4f9a5d8) Sip CallId 0b6e0f8010b374346c14873db22ce4d1
8602423mS SIP Reg/Opt Rx: 18
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 192.168.3.10:5060;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867;rport=1026
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
Server: kamailio (5.7.5 (x86_64/linux))
Content-Length: 0

8602423mS Sip: c0a8030a30000472 0.805307506.0 -1 SIPTrunk Endpoint(f4f98ac8) Process SIP response dialog f4f98ac8, method REGISTER, CodeNum 100 in state SIPDialog::INITIAL(0)
8602511mS SIP Rx: UDP 199.255.120.176:5090 -> 192.168.3.10:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.10:5060;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867;rport=1026
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>;tag=1a3aba47024e8e77df2d6ef03cfcd6ae-a1e90000
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
WWW-Authenticate: Digest realm="10.13.120.93", nonce="Z1t7U2dbeifkF3zQBQozZvC9UYCbdiel", algorithm=MD5
Content-Length: 0

8602513mS Sip: Find End Point c0a8030a30000472 0.805307506.0 -1 SIPTrunk Endpoint (f4f9a5d8) Sip CallId 0b6e0f8010b374346c14873db22ce4d1
8602514mS SIP Reg/Opt Rx: 18
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.10:5060;branch=z9hG4bKf13ba2f1fb8a006cf0a30829c9b00867;rport=1026
From: <sip:15878024935@199.255.120.146>;tag=da53b825dc8f295b
To: <sip:15878024935@199.255.120.146>;tag=1a3aba47024e8e77df2d6ef03cfcd6ae-a1e90000
Call-ID: 0b6e0f8010b374346c14873db22ce4d1
CSeq: 1134849434 REGISTER
WWW-Authenticate: Digest realm="10.13.120.93", nonce="Z1t7U2dbeifkF3zQBQozZvC9UYCbdiel", algorithm=MD5
Content-Length: 0

 

[Menniss]

That is interesting that you got a reply and I didn't. However my advice is still that same you should contact the carrier and as for there assistance.