jawaid Posted November 3, 2021 Report Share Posted November 3, 2021 I am at a loss to figure out why when I dial a 3 digit service number, when the call is sent to my trunk provider the number is changed. For example if I dial 111 (for NHS Helpline), when the call reaches the provider it seems to be translated to 0011@provider_domain. I have checked the logs an upto the point the call is sent to the provider everything is shown correctly, the Sip To: shows sip:111@mydomain In my dialplan all I have is 111 with no translation/replacement string. I have also set the 'rewrite global numbers' in the SIP Trunk Setting to 'don't rewrite'. The domain country is set to 44 for the UK. I have contacted my provider and they keep telling me it is something at my end. I am wondering if because the system is built around the USA environment, it is ignoring the country and still prefixing the 111, thinking it is an international or national number in the USA. The same thing happens if I prefix a number with '141' to hide the CLI Any pointers/advice much appreciated. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 3, 2021 Report Share Posted November 3, 2021 The INVITE to the provider is what needs to be right. If there is a 0011@provider_domain yes then its a problem with the PBX setup. 0011 is the international prefix for New Zealand. I doubt that this is problem here. I would crank up the log levels to 9 on trunk, sip, general and try this again. Then we might be able where the number translation went wrong. Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 3, 2021 Author Report Share Posted November 3, 2021 That's what I have done and noticed that the invite to the provider has the 0011@provider_domain. However what is even stranger, is that I have a different provider that I have used for testing purposes in the past, and if I route the dialplan for 111 to use that provider, the call goes through fine, without any translations. I have checked the SIP Trunk settings for both and they are identical. So is it the PBX setup that is wrong or the sip provider side? I have got in touch with the provider, sent them pcap traces and they think it is the configuration at my end, but I am not so sure. Catch 22 at the minute. Is there something in the backend of the PBX that differentiates based on the SIP Provider? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 3, 2021 Report Share Posted November 3, 2021 If one trunk works and the other does not, well that would be a sign to look into the trunk settings. I would especially pay attention if there was a separate country code in the trunk and if the number presentation makes sense. Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 4, 2021 Author Report Share Posted November 4, 2021 I have checked the Trunk settings for both and the same entries are setup with the same values. In particular the Rewrite Global Numbers and Country code are the same. However on the SIP Trunk that works there are options for P-Charging-Vector and Diversion Header, which are not available on the SIP Trunk that does not work. Not sure if this would be relevant or not. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 4, 2021 Report Share Posted November 4, 2021 6 hours ago, jawaid said: However on the SIP Trunk that works there are options for P-Charging-Vector and Diversion Header, which are not available on the SIP Trunk that does not work. Not sure if this would be relevant or not. That is not relevant. I would really try to go along the log messages and see where it morphed into the 0011. Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 4, 2021 Author Report Share Posted November 4, 2021 Here is a snapshot of the log file which show the first occurrence of 0011@provider.co.uk I have taken out all references to actual domains etc [5] 7:48:41.194 PACK: SIP Rx 92.28.69.110:61933: INVITE sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp SIP/2.0 Via: SIP/2.0/TCP xxx.xxx.xxx.xxx;branch=z9hG4bK59344827C28CE59A From: "JK" <sip:3501@pbx.mydomain.co.uk>;tag=5D9267CB-AEC11D5E To: <sip:111@pbx.mydomain.co.uk;user=phone> CSeq: 2 INVITE Call-ID: e1dd51cbeca3a4d0238b2665807443b4 Contact: <sip:3501@xxx.xxx.xxx.xxx;transport=tcp> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER User-Agent: PolycomVVX-VVX_400-UA/5.9.6.2996 Accept-Language: en-gb,en;q=0.9 Supported: replaces,100rel Allow-Events: conference,talk,hold Authorization: Digest username="0004F27443B4", realm="pbx.mydomain.co.uk", nonce="be44b69c5dd59f2e722589354760d4e8", uri="sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp", response="5c7f5c26cb0a3ae52e133463cf66c7df", algorithm=MD5 Max-Forwards: 70 Content-Type: application/sdp Content-Length: 350 v=0 o=- 1635925721 1635925721 IN IP4 xxx.xxx.xxx.xxx s=Polycom IP Phone c=IN IP4 xxx.xxx.xxx.xxx t=0 0 a=sendrecv m=audio 2224 RTP/AVP 9 102 0 8 18 127 a=rtpmap:9 G722/8000 a=rtpmap:102 G7221/16000 a=fmtp:102 bitrate=32000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:127 telephone-event/8000 [8] 7:48:41.194 SIP: Tagging request with existing tag [8] 7:48:41.194 MEDI: Port 10: Added predefined codec 6 (mapped to 9) [8] 7:48:41.194 MEDI: Port 10: Added predefined codec 2 (mapped to 0) [8] 7:48:41.194 MEDI: Port 10: Added predefined codec 3 (mapped to [8] 7:48:41.194 MEDI: Port 10: Added predefined codec 7 (mapped to 18) [8] 7:48:41.194 MEDI: Port 10: Added rtpmap codec 13 (mapped to 102) [8] 7:48:41.194 MEDI: Port 10: Added rtpmap codec 1 (mapped to 127) [6] 7:48:41.194 MEDI: Port 10: Sending RTP to xxx.xxx.xxx.xxx:2224, codec not set yet [5] 7:48:41.196 APP: Last message repeated 2 times [8] 7:48:41.196 APP: Call 5: Notify state idle [9] 7:48:41.196 APP: Dialog state for user 3501 has not changed [4] 7:48:41.196 APP: Last message repeated 2 times [8] 7:48:41.196 APP: Call 5: Disconnect all others except leg 9 [8] 7:48:41.196 APP: Call 5: Dialing star code 111 [4] 7:48:41.198 APP: Last message repeated 2 times [9] 7:48:41.198 APP: Dialog state for user 3501 has not changed [8] 7:48:41.198 APP: Call 5: Disconnect all others except leg 9 [9] 7:48:41.198 TRUN: Dialplan: Simple match 111 to 111 [9] 7:48:41.199 TRUN: Dialplan: Evaluating 999 against 111@pbx.mydomain.co.uk [9] 7:48:41.199 TRUN: Dialplan: Evaluating 112 against 111@pbx.mydomain.co.uk [9] 7:48:41.199 TRUN: Dialplan: Simple match 111 to 111 [9] 7:48:41.199 TRUN: Dialplan: Evaluating 111 against 111@pbx.mydomain.co.uk [5] 7:48:41.199 TRUN: Last message repeated 2 times [8] 7:48:41.199 TRUN: Using rule set "ext-eani dom-eani ext-epid" for user 3501 [8] 7:48:41.199 TRUN: Processing rule ext-eani [9] 7:48:41.199 TRUN: Placeholder ext-eani for user 3501 is [8] 7:48:41.199 TRUN: Processing rule dom-eani [9] 7:48:41.199 TRUN: Placeholder dom-eani is [8] 7:48:41.199 TRUN: Processing rule ext-epid [4] 7:48:41.199 TRUN: Last message repeated 2 times [8] 7:48:41.199 TRUN: Using rule set "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" for user 3501 [8] 7:48:41.199 TRUN: Processing rule acd-ani [8] 7:48:41.199 TRUN: Processing rule ext-ani [9] 7:48:41.199 TRUN: Placeholder ext-ani for user 3501 is 441234567890 [8] 7:48:41.199 TRUN: Using 441234567890 JK [9] 7:48:41.201 APP: Dialog state for user 3501 has changed [5] 7:48:41.202 PACK: SIP Tx 92.28.69.110:61933: SIP/2.0 100 Trying Via: SIP/2.0/TCP xxx.xxx.xxx.xxx;branch=z9hG4bK59344827C28CE59A;rport=61933;received=92.28.69.110 From: "JK" <sip:3501@pbx.mydomain.co.uk>;tag=5D9267CB-AEC11D5E To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=my0t8221jn Call-ID: e1dd51cbeca3a4d0238b2665807443b4 CSeq: 2 INVITE Content-Length: 0 [7] 7:48:41.203 MEDI: Port 10: Set codecs to 8 0 preference count 3 [7] 7:48:41.203 MEDI: Port 11: Set codecs to 0 8 preference count 3 [9] 7:48:41.203 SIP: Using outbound proxy sip:provider.co.uk because of registration trunk [8] 7:48:41.203 MEDI: Port 11: state code from 0 to 100 [9] 7:48:41.203 MEDI: Port 11: Adding codec PCMU/8000 to available list [9] 7:48:41.203 MEDI: Port 11: Adding codec PCMA/8000 to available list [9] 7:48:41.203 MEDI: Port 11: Update codecs preference size 3, available codecs size 3 [7] 7:48:41.204 MEDI: Port 11: Allocated ports 51392 and 51393 [8] 7:48:41.204 MEDI: Port 10: state code from 0 to 183 [8] 7:48:41.204 MEDI: Port 10: Ignore double SDP [5] 7:48:41.205 PACK: SIP Tx xxx.xxx.xxx.xxx:5060:INVITE sip:0011@provider.co.uk SIP/2.0 Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK-2d7e074cf81f4481c121b5fd6b74d8ce;rport From: <sip:2639898656@provider.co.uk>;tag=1493144771 To: <sip:0011@provider.co.uk> Call-ID: 3c75be72@pbx CSeq: 17136 INVITE Max-Forwards: 70 Contact: <sip:2639898656@xxx.xxx.xxx.xxx:5060;transport=udp> Allow-Events: refer Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/68.0.2 Remote-Party-ID: <sip:my_ddi_number@provider.co.uk> Content-Type: application/sdp Content-Length: 232 Let me know if this helps. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 4, 2021 Report Share Posted November 4, 2021 Ok what is weird is that it considers this to be a star code or shall we say special number. Is 111 on the list of emergency numbers? Or did you maybe accidentally put a 111 into the list of star codes? Also what is in the "ht" trunk setting (use the text view for the trunk settings)? Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 5, 2021 Author Report Share Posted November 5, 2021 111 is in the list of emergency numbers. No setting in star codes for 111. The "ht" setting is ht: <{request-uri}> Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 5, 2021 Report Share Posted November 5, 2021 Ok we need to dig deeper into the emergency number topic then... Did you maybe enter the 0011 somewhere as the emergency number destination? That would explain everything... Except why it does not cause a problem when dialing the other trunk Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 6, 2021 Author Report Share Posted November 6, 2021 This is the entry for Emergency numbers under the tenants general settings: 101; 105; 111; 112; 119; 999 then then the numbers are in the dialplan to break out via the provider. Is there another setting somewhere else that I need to check? Quote Link to comment Share on other sites More sharing options...
Support Posted November 8, 2021 Report Share Posted November 8, 2021 Could you set the admin log level to 9 for "trunks" and attach them here? Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 9, 2021 Author Report Share Posted November 9, 2021 I have made a single test call and the log as is follows: [8] 7:14:23.073 Find trunk: Message RURI user 111, host pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Trunk 1 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression 300 for trunk 1ⓘ [9] 7:14:23.074 Find trunk: Trunk 10 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 10ⓘ [9] 7:14:23.074 Find trunk: Trunk 12 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 12ⓘ [9] 7:14:23.074 Find trunk: Trunk 13 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 13ⓘ [9] 7:14:23.074 Find trunk: Trunk 14 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 14ⓘ [9] 7:14:23.074 Find trunk: Trunk 15 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 15ⓘ [9] 7:14:23.074 Find trunk: Trunk 16 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 16ⓘ [9] 7:14:23.074 Find trunk: Trunk 17 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 17ⓘ [9] 7:14:23.074 Find trunk: Trunk 19 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 19ⓘ [9] 7:14:23.074 Find trunk: Trunk 2 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression for trunk 2ⓘ [9] 7:14:23.074 Find trunk: Trunk 20 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 20ⓘ [9] 7:14:23.074 Find trunk: Trunk 21 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 21ⓘ [9] 7:14:23.074 Find trunk: Trunk 22 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 22ⓘ [9] 7:14:23.074 Find trunk: Trunk 23 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 23ⓘ [9] 7:14:23.074 Find trunk: Trunk 24 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 24ⓘ [9] 7:14:23.074 Find trunk: Trunk 25 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 25ⓘ [9] 7:14:23.074 Find trunk: Trunk 26 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 26ⓘ [9] 7:14:23.074 Find trunk: Trunk 27 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 27ⓘ [9] 7:14:23.074 Find trunk: Trunk 28 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 28ⓘ [9] 7:14:23.074 Find trunk: Trunk 3 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression for trunk 3ⓘ [9] 7:14:23.074 Find trunk: Trunk 4 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression for trunk 4ⓘ [9] 7:14:23.074 Find trunk: Trunk 5 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression for trunk 5ⓘ [9] 7:14:23.074 Find trunk: Trunk 6 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression for trunk 6ⓘ [9] 7:14:23.074 Find trunk: Trunk 9 matches domain pbx.mydomain.co.ukⓘ [9] 7:14:23.074 Find trunk: Try expression ! for trunk 9ⓘ [8] 7:14:23.074 Could not find a trunk (24 trunks)ⓘ [5] 7:14:23.310 Port 129: Incoming call in domain pbx.mydomain.co.uk on port 129 extension 3501ⓘ [5] 7:14:23.311 Last message repeated 2 timesⓘ [5] 7:14:23.311 Call 1: New call created with Call-ID 129ⓘ [4] 7:14:23.311 Call 1: Dial number 111 from user 3501 and dial plan Defaultⓘ [4] 7:14:23.313 Calling emergency number 111 from extension 3501ⓘ [9] 7:14:23.313 Dialplan: Simple match 111 to 111ⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Dialplan: Evaluating 999 against 111@pbx.mydomain.co.ukⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Dialplan: Evaluating 112 against 111@pbx.mydomain.co.ukⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Dialplan: Simple match 111 to 111ⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Dialplan: Evaluating 111 against 111@pbx.mydomain.co.ukⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [5] 7:14:23.314 Dialplan "Default": Match 111@pbx.mydomain.co.uk to sip:111@provider.co.uk;user=phone on trunk Provider-Trunk Outboundⓘ [5] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Using rule set "ext-eani dom-eani ext-epid" for user 3501ⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Processing rule ext-eaniⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Placeholder ext-eani for user 3501 is ⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Processing rule dom-eaniⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Placeholder dom-eani is ⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Processing rule ext-epidⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [4] 7:14:23.314 No ANI found for emergency call, trying regular ANIⓘ [4] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Using rule set "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" for user 3501ⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Processing rule acd-aniⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Processing rule ext-aniⓘ [8] 7:14:23.314 Last message repeated 2 timesⓘ [9] 7:14:23.314 Placeholder ext-ani for user 3501 is 441234567890ⓘ [9] 7:14:23.314 Last message repeated 2 timesⓘ [8] 7:14:23.314 Using 441234567890 Jawaidⓘ [5] 7:14:25.506 INVITE Response 404 Not Found: Terminate fd47e73a@pbxⓘ [5] 7:14:32.597 HTTP 3.220.57.224: Alert Fatal (2): Handshake failure (40)ⓘ Quote Link to comment Share on other sites More sharing options...
Support Posted November 9, 2021 Report Share Posted November 9, 2021 Could you also set the logs for "calls" and attach them, sorry. Or maybe give us a call with Anydesk ID handy and we can go from there. Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 11, 2021 Author Report Share Posted November 11, 2021 Here is the log with both trunks and calls enabled: 7:05:28.540 Find trunk: Trunk 14 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 14ⓘ [9] 7:05:28.540 Find trunk: Trunk 15 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 15ⓘ [9] 7:05:28.540 Find trunk: Trunk 16 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 16ⓘ [9] 7:05:28.540 Find trunk: Trunk 17 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 17ⓘ [9] 7:05:28.540 Find trunk: Trunk 19 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 19ⓘ [9] 7:05:28.540 Find trunk: Trunk 2 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression for trunk 2ⓘ [9] 7:05:28.540 Find trunk: Trunk 20 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 20ⓘ [9] 7:05:28.540 Find trunk: Trunk 21 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 21ⓘ [9] 7:05:28.540 Find trunk: Trunk 22 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 22ⓘ [9] 7:05:28.540 Find trunk: Trunk 23 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 23ⓘ [9] 7:05:28.540 Find trunk: Trunk 24 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 24ⓘ [9] 7:05:28.540 Find trunk: Trunk 25 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 25ⓘ [9] 7:05:28.540 Find trunk: Trunk 26 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 26ⓘ [9] 7:05:28.540 Find trunk: Trunk 27 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 27ⓘ [9] 7:05:28.540 Find trunk: Trunk 28 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 28ⓘ [9] 7:05:28.540 Find trunk: Trunk 3 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression for trunk 3ⓘ [9] 7:05:28.540 Find trunk: Trunk 4 matches domain pbx.mydomain.co.ukⓘ I can give you a call tonight at 19:30 my time [9] 7:05:28.540 Find trunk: Try expression for trunk 4ⓘ [9] 7:05:28.540 Find trunk: Trunk 5 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression for trunk 5ⓘ [9] 7:05:28.540 Find trunk: Trunk 6 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression for trunk 6ⓘ [9] 7:05:28.540 Find trunk: Trunk 9 matches domain pbx.mydomain.co.ukⓘ [9] 7:05:28.540 Find trunk: Try expression ! for trunk 9ⓘ [8] 7:05:28.540 Could not find a trunk (24 trunks)ⓘ [5] 7:05:28.541 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 100 Trying Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bK426b11beA4E1D529;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=6136dda9c3 Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 1 INVITE Content-Length: 0 [5] 7:05:28.542 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 401 Authentication Required Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bK426b11beA4E1D529;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=6136dda9c3 Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 1 INVITE User-Agent: Vodia-PBX/68.0.2 WWW-Authenticate: Digest realm="pbx.mydomain.co.uk",nonce="70ecac59df11e9da0abaab879ffeec65",domain="sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp",algorithm=MD5 Content-Length: 0 [5] 7:05:28.727 SIP Rx 92.28.69.110:57731:ⓘ ACK sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bK426b11beA4E1D529 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=6136dda9c3 CSeq: 1 ACK Call-ID: e3c8f2c03c51500ae8f4391f167443b4 Contact: <sip:3501@172.16.2.192;transport=tcp> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER User-Agent: PolycomVVX-VVX_400-UA/5.9.6.2996 Accept-Language: en-gb,en;q=0.9 Max-Forwards: 70 Content-Length: 0 [5] 7:05:28.783 SIP Rx 92.28.69.110:57731:ⓘ INVITE sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bKa6fbcc2cC3B38587 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone> CSeq: 2 INVITE Call-ID: e3c8f2c03c51500ae8f4391f167443b4 Contact: <sip:3501@172.16.2.192;transport=tcp> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER User-Agent: PolycomVVX-VVX_400-UA/5.9.6.2996 Accept-Language: en-gb,en;q=0.9 Supported: replaces,100rel Allow-Events: conference,talk,hold Authorization: Digest username="0004F27443B4", realm="pbx.mydomain.co.uk", nonce="70ecac59df11e9da0abaab879ffeec65", uri="sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp", response="87c8c55a51201a09fc28e4290e513284", algorithm=MD5 Max-Forwards: 70 Content-Type: application/sdp Content-Length: 350 v=0 o=- 1636614328 1636614328 IN IP4 172.16.2.192 s=Polycom IP Phone c=IN IP4 172.16.2.192 t=0 0 a=sendrecv m=audio 2262 RTP/AVP 9 102 0 8 18 127 a=rtpmap:9 G722/8000 a=rtpmap:102 G7221/16000 a=fmtp:102 bitrate=32000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:127 telephone-event/8000 [5] 7:05:28.785 Port 763: Incoming call in domain pbx.mydomain.co.uk on port 763 extension 3501ⓘ [5] 7:05:28.785 Last message repeated 2 timesⓘ [5] 7:05:28.785 Call 9: New call created with Call-ID 763ⓘ [4] 7:05:28.786 Call 9: Dial number 111 from user 3501 and dial plan Defaultⓘ [4] 7:05:28.788 Calling emergency number 111 from extension 3501ⓘ [9] 7:05:28.788 Dialplan: Simple match 111 to 111ⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [9] 7:05:28.789 Dialplan: Evaluating 999 against 111@pbx.mydomain.co.ukⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [9] 7:05:28.789 Dialplan: Evaluating 112 against 111@pbx.mydomain.co.ukⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [9] 7:05:28.789 Dialplan: Simple match 111 to 111ⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [9] 7:05:28.789 Dialplan: Evaluating 111 against 111@pbx.mydomain.co.ukⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [5] 7:05:28.789 Dialplan "Default": Match 111@pbx.mydomain.co.uk to sip:111@provider.co.uk;user=phone on trunk UC-Reseller Outboundⓘ [5] 7:05:28.789 Last message repeated 2 timesⓘ [8] 7:05:28.789 Using rule set "ext-eani dom-eani ext-epid" for user 3501ⓘ [8] 7:05:28.789 Last message repeated 2 timesⓘ [8] 7:05:28.789 Processing rule ext-eaniⓘ [8] 7:05:28.789 Last message repeated 2 timesⓘ [9] 7:05:28.789 Placeholder ext-eani for user 3501 is ⓘ [9] 7:05:28.789 Last message repeated 2 timesⓘ [8] 7:05:28.790 Processing rule dom-eaniⓘ [8] 7:05:28.790 Last message repeated 2 timesⓘ [9] 7:05:28.790 Placeholder dom-eani is ⓘ [9] 7:05:28.790 Last message repeated 2 timesⓘ [8] 7:05:28.790 Processing rule ext-epidⓘ [8] 7:05:28.790 Last message repeated 2 timesⓘ [4] 7:05:28.790 No ANI found for emergency call, trying regular ANIⓘ [4] 7:05:28.790 Last message repeated 2 timesⓘ [8] 7:05:28.790 Using rule set "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" for user 3501ⓘ [8] 7:05:28.790 Last message repeated 2 timesⓘ [8] 7:05:28.790 Processing rule acd-aniⓘ [8] 7:05:28.790 Last message repeated 2 timesⓘ [8] 7:05:28.790 Processing rule ext-aniⓘ [8] 7:05:28.790 Last message repeated 2 timesⓘ [9] 7:05:28.790 Placeholder ext-ani for user 3501 is 441234567890ⓘ [9] 7:05:28.790 Last message repeated 2 timesⓘ [8] 7:05:28.790 Using 441234567890 Jawaidⓘ [5] 7:05:28.794 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 100 Trying Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bKa6fbcc2cC3B38587;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 2 INVITE Content-Length: 0 [5] 7:05:28.797 SIP Tx 51.38.75.205:5060:ⓘ INVITE sip:0011@provider.co.uk SIP/2.0 Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-5f1ffcb014dc4be2ea46f487e7a88047;rport From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk> Call-ID: f4aceb65@pbx CSeq: 26528 INVITE Max-Forwards: 70 Contact: <sip:2639898656@107.181.136.136:5060;transport=udp> Allow-Events: refer Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/68.0.2 Remote-Party-ID: <sip:0041282573501@provider.co.uk> Content-Type: application/sdp Content-Length: 232 v=0 o=- 2058009292 2058009292 IN IP4 107.181.136.136 s=- c=IN IP4 107.181.136.136 t=0 0 m=audio 51608 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 7:05:28.798 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bKa6fbcc2cC3B38587;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 2 INVITE Contact: <sip:3501@107.181.136.136:5060;transport=tcp> Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/68.0.2 Require: 100rel RSeq: 1 Content-Type: application/sdp Content-Length: 265 v=0 o=- 18185866 18185866 IN IP4 107.181.136.136 s=- c=IN IP4 107.181.136.136 t=0 0 m=audio 50310 RTP/AVP 8 0 127 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:127 telephone-event/8000 a=fmtp:127 0-15 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 7:05:28.800 SIP Rx 51.38.75.205:5060:ⓘ SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-5f1ffcb014dc4be2ea46f487e7a88047;rport=5060;received=107.181.136.136 From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk> Call-ID: f4aceb65@pbx CSeq: 26528 INVITE Content-Length: 0 [5] 7:05:28.806 SIP Rx 51.38.75.205:5060:ⓘ SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 107.181.136.136:5060;received=107.181.136.136;branch=z9hG4bK-5f1ffcb014dc4be2ea46f487e7a88047;rport=5060 From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk>;tag=as2040a467 Call-ID: f4aceb65@pbx CSeq: 26528 INVITE Server: MERLIN DC23-1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="004e81cd" Content-Length: 0 [5] 7:05:28.807 SIP Tx 51.38.75.205:5060:ⓘ ACK sip:0011@provider.co.uk SIP/2.0 Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-5f1ffcb014dc4be2ea46f487e7a88047;rport From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk>;tag=as2040a467 Call-ID: f4aceb65@pbx CSeq: 26528 ACK Max-Forwards: 70 Content-Length: 0 [5] 7:05:28.807 SIP Tx 51.38.75.205:5060:ⓘ INVITE sip:0011@provider.co.uk SIP/2.0 Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-b127185bf3954e355dcf2ce9b457df1e;rport From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk> Call-ID: f4aceb65@pbx CSeq: 26529 INVITE Max-Forwards: 70 Contact: <sip:2639898656@107.181.136.136:5060;transport=udp> Allow-Events: refer Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/68.0.2 Remote-Party-ID: <sip:0041282573501@provider.co.uk> Authorization: Digest realm="asterisk",nonce="004e81cd",response="45095f1ec48879f151f636bc56a41dd5",username="2639898656",uri="sip:0011@provider.co.uk",algorithm=MD5 Content-Type: application/sdp Content-Length: 232 v=0 o=- 2058009292 2058009292 IN IP4 107.181.136.136 s=- c=IN IP4 107.181.136.136 t=0 0 m=audio 51608 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 7:05:28.809 SIP Rx 51.38.75.205:5060:ⓘ SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-b127185bf3954e355dcf2ce9b457df1e;rport=5060;received=107.181.136.136 From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk> Call-ID: f4aceb65@pbx CSeq: 26529 INVITE Content-Length: 0 [5] 7:05:28.931 SIP Rx 92.28.69.110:57731:ⓘ PRACK sip:3501@107.181.136.136:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bK3dbb4d287CC16B63 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex CSeq: 3 PRACK Call-ID: e3c8f2c03c51500ae8f4391f167443b4 Contact: <sip:3501@172.16.2.192;transport=tcp> User-Agent: PolycomVVX-VVX_400-UA/5.9.6.2996 Accept-Language: en-gb,en;q=0.9 RAck: 1 2 INVITE Authorization: Digest username="0004F27443B4", realm="pbx.mydomain.co.uk", nonce="70ecac59df11e9da0abaab879ffeec65", uri="sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp", response="a5f5dfd1d8e5bf2c77fda15c1b1179ff", algorithm=MD5 Max-Forwards: 70 Content-Length: 0 [5] 7:05:28.931 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 200 Ok Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bK3dbb4d287CC16B63;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 3 PRACK Contact: <sip:3501@107.181.136.136:5060;transport=tcp> User-Agent: Vodia-PBX/68.0.2 P-Asserted-Identity: <sip:111@pbx.mydomain.co.uk> Content-Length: 0 [5] 7:05:30.913 SIP Rx 51.38.75.205:5060:ⓘ SIP/2.0 404 Not Found Via: SIP/2.0/UDP 107.181.136.136:5060;received=107.181.136.136;branch=z9hG4bK-b127185bf3954e355dcf2ce9b457df1e;rport=5060 From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk>;tag=as232d0991 Call-ID: f4aceb65@pbx CSeq: 26529 INVITE Server: MERLIN DC23-1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Length: 0 [5] 7:05:30.914 INVITE Response 404 Not Found: Terminate f4aceb65@pbxⓘ [5] 7:05:30.914 SIP Tx 51.38.75.205:5060:ⓘ ACK sip:0011@provider.co.uk SIP/2.0 Via: SIP/2.0/UDP 107.181.136.136:5060;branch=z9hG4bK-b127185bf3954e355dcf2ce9b457df1e;rport From: <sip:2639898656@provider.co.uk>;tag=421641749 To: <sip:0011@provider.co.uk>;tag=as232d0991 Call-ID: f4aceb65@pbx CSeq: 26529 ACK Max-Forwards: 70 Contact: <sip:2639898656@107.181.136.136:5060;transport=udp> Remote-Party-ID: <sip:0041282573501@provider.co.uk> Content-Length: 0 [5] 7:05:30.919 SIP Tx 92.28.69.110:57731:ⓘ SIP/2.0 404 Not Found Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bKa6fbcc2cC3B38587;rport=57731;received=92.28.69.110 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex Call-ID: e3c8f2c03c51500ae8f4391f167443b4 CSeq: 2 INVITE Contact: <sip:3501@107.181.136.136:5060;transport=tcp> Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/68.0.2 P-Asserted-Identity: <sip:111@pbx.mydomain.co.uk> Content-Length: 0 [5] 7:05:30.942 SIP Rx 92.28.69.110:57731:ⓘ ACK sip:111@pbx.mydomain.co.uk:5060;user=phone;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 172.16.2.192;branch=z9hG4bKa6fbcc2cC3B38587 From: "Jawaid" <sip:3501@pbx.mydomain.co.uk>;tag=B982E8B0-F21B492B To: <sip:111@pbx.mydomain.co.uk;user=phone>;tag=osxegufdex CSeq: 2 ACK Call-ID: e3c8f2c03c51500ae8f4391f167443b4 Contact: <sip:3501@172.16.2.192;transport=tcp> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER User-Agent: PolycomVVX-VVX_400-UA/5.9.6.2996 Accept-Language: en-gb,en;q=0.9 Max-Forwards: 70 Content-Length: 0 Let me know when you are available after 14:30 your time, and I shall call you. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 11, 2021 Report Share Posted November 11, 2021 So we finally had the opportunity to reproduce this. The problem was specific to the UC Reseller trunk template. We'll fix this in the next build, if you want to try you can use the 68.0.5.beta build (only CentOS64 and Debian64). Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 12, 2021 Author Report Share Posted November 12, 2021 Thanks, glad you found the issue. Is it possible for you to share what the fix was? Is this a template that I can customise? Will update once I have tried the build. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 13, 2021 Report Share Posted November 13, 2021 The UC reseller trunk has special code because their headers require a mix of number presentations that cannot be setup with there regular settings. There was a bug with the representation on numbers that are not regular phone numbers. It's not easy to fix it with a setting. Quote Link to comment Share on other sites More sharing options...
jawaid Posted November 15, 2021 Author Report Share Posted November 15, 2021 I have updated the system to v68.0.5-beta and can now make calls to 111, and other 3 digit numbers. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.