cei66 Posted January 31, 2012 Report Share Posted January 31, 2012 Hello , Now the trunk is working but the Display Name of the trunk don't work it put "anonymous" OVH my sip provider said to me that it's probally a pb of ring cadence Thanks Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 31, 2012 Report Share Posted January 31, 2012 4.5 has a lot more flexibility with the SIP header presentation than all previous version. We tried to keep it backwards compatible, but it seems there is something special for you. http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers has the information what is possible. Maybe you can just post the INVITE packet here along with the name of the service provider, so that we can find a solution also for those who use the same service provider. Quote Link to comment Share on other sites More sharing options...
cei66 Posted January 31, 2012 Author Report Share Posted January 31, 2012 4.5 has a lot more flexibility with the SIP header presentation than all previous version. We tried to keep it backwards compatible, but it seems there is something special for you. http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers has the information what is possible. Maybe you can just post the INVITE packet here along with the name of the service provider, so that we can find a solution also for those who use the same service provider. here is the log file the provider is OVH France error "SIP/2.0 403 Wrong login or password" the call who is ok is whith the trunk who was create with the odl version (but i was obliged to retype the password and save the trunk config ) log-2012-01-31.txt Quote Link to comment Share on other sites More sharing options...
Vodia support Posted January 31, 2012 Report Share Posted January 31, 2012 here is the log file the provider is OVH France error "SIP/2.0 403 Wrong login or password" the call who is ok is whith the trunk who was create with the odl version (but i was obliged to retype the password and save the trunk config ) We are sending the User/Pass on the invite so somethings up? Can you recreate the trunk and they try again. [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 407 authentication required Call-ID: f5324e4f@pbx Contact: <sip:0486688001@91.121.129.17:5060;user=phone> CSeq: 20957 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 Proxy-Authenticate: Digest realm="sip.ovh.net",nonce="085d90ab445fd6f22fd5ca59158a95d0",opaque="085c3e0d6890b34",stale=false,algorithm=MD5 Record-Route: <sip:91.121.129.20:5060;transport=udp;lr> To: "0486688001" <sip:0486688001@pbx.company.com;user=phone>;tag=00-07383-085d97f4-13d15b8e3 Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-476f609b2f865e83ac8b945cd6635f5a Allow: UPDATE,REFER,INFO Server: Cirpack/v4.42a (gw_sip) Content-Length: 0 [5] 20120131151306: SIP Tx udp:91.121.129.20:5060: INVITE sip:0486688001@sip.ovh.net;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec;rport From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 To: "0486688001" <sip:0486688001@pbx.company.com;user=phone> Call-ID: f5324e4f@pbx CSeq: 20958 INVITE Max-Forwards: 70 Contact: <sip:0033411930139@192.168.1.200:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/2011-4.5.0.1016 Alpha Monocerotids P-Asserted-Identity: <sip:0033411930139@sip.ovh.net> Privacy: id P-Charging-Vector: icid-value=;icid-generated-at=192.168.1.200;orig-ioi=pbx.company.com Proxy-Authorization: Digest realm="sip.ovh.net",nonce="085d90ab445fd6f22fd5ca59158a95d0",response="4b60c5a793172824776c0766fd32c914",username="0033411930139",uri="sip:0486688001@sip.ovh.net;user=phone",opaque="085c3e0d6890b34",algorithm=MD5 Content-Type: application/sdp Content-Length: 231 v=0 o=- 44713 44713 IN IP4 192.168.1.200 s=- c=IN IP4 192.168.1.200 t=0 0 m=audio 55210 RTP/AVP 8 101 a=rtpmap:8 pcma/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 100 Trying Call-ID: f5324e4f@pbx CSeq: 20958 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 To: "0486688001" <sip:0486688001@pbx.company.com;user=phone> Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec Content-Length: 0 [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 403 Wrong login or password Call-ID: f5324e4f@pbx Contact: <sip:91.121.129.17:5060> CSeq: 20958 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 Record-Route: <sip:91.121.129.20:5060;transport=udp;lr> To: "0486688001" <sip:0486688001@pbx.company.com;user=phone>;tag=00-07369-085d9807-6be51daf5 Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec Allow: UPDATE,REFER,INFO Reason: q.850;cause=1 Server: Cirpack/v4.42a (gw_sip) Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
cei66 Posted January 31, 2012 Author Report Share Posted January 31, 2012 Hello , i ve got the problem with the second trunk who is completely create with the 4.5 version , with the same trunk created with the 4.3 version i only have to retype the password when i launch the 4.5 version and then it's ok. the log file is with : first OVH39 trunk(created with 4.3+ retype password)ok second OVH4139 trunk (created with 4.5) error Quote Link to comment Share on other sites More sharing options...
shopcomputer Posted January 31, 2012 Report Share Posted January 31, 2012 We are sending the User/Pass on the invite so somethings up? Can you recreate the trunk and they try again. [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 407 authentication required Call-ID: f5324e4f@pbx Contact: <sip:0486688001@91.121.129.17:5060;user=phone> CSeq: 20957 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 Proxy-Authenticate: Digest realm="sip.ovh.net",nonce="085d90ab445fd6f22fd5ca59158a95d0",opaque="085c3e0d6890b34",stale=false,algorithm=MD5 Record-Route: <sip:91.121.129.20:5060;transport=udp;lr> To: "0486688001" <sip:0486688001@pbx.company.com;user=phone>;tag=00-07383-085d97f4-13d15b8e3 Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-476f609b2f865e83ac8b945cd6635f5a Allow: UPDATE,REFER,INFO Server: Cirpack/v4.42a (gw_sip) Content-Length: 0 [5] 20120131151306: SIP Tx udp:91.121.129.20:5060: INVITE sip:0486688001@sip.ovh.net;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.200:5060;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec;rport From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 To: "0486688001" <sip:0486688001@pbx.company.com;user=phone> Call-ID: f5324e4f@pbx CSeq: 20958 INVITE Max-Forwards: 70 Contact: <sip:0033411930139@192.168.1.200:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/2011-4.5.0.1016 Alpha Monocerotids P-Asserted-Identity: <sip:0033411930139@sip.ovh.net> Privacy: id P-Charging-Vector: icid-value=;icid-generated-at=192.168.1.200;orig-ioi=pbx.company.com Proxy-Authorization: Digest realm="sip.ovh.net",nonce="085d90ab445fd6f22fd5ca59158a95d0",response="4b60c5a793172824776c0766fd32c914",username="0033411930139",uri="sip:0486688001@sip.ovh.net;user=phone",opaque="085c3e0d6890b34",algorithm=MD5 Content-Type: application/sdp Content-Length: 231 v=0 o=- 44713 44713 IN IP4 192.168.1.200 s=- c=IN IP4 192.168.1.200 t=0 0 m=audio 55210 RTP/AVP 8 101 a=rtpmap:8 pcma/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 100 Trying Call-ID: f5324e4f@pbx CSeq: 20958 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 To: "0486688001" <sip:0486688001@pbx.company.com;user=phone> Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec Content-Length: 0 [5] 20120131151306: SIP Rx udp:91.121.129.20:5060: SIP/2.0 403 Wrong login or password Call-ID: f5324e4f@pbx Contact: <sip:91.121.129.17:5060> CSeq: 20958 INVITE From: "LAURENT:45" <sip:45@pbx.company.com;user=phone>;tag=38247 Record-Route: <sip:91.121.129.20:5060;transport=udp;lr> To: "0486688001" <sip:0486688001@pbx.company.com;user=phone>;tag=00-07369-085d9807-6be51daf5 Via: SIP/2.0/UDP 192.168.1.200:5060;received=213.41.241.100;rport=50628;branch=z9hG4bK-c5908628c5b8af81f250d9b01af49dec Allow: UPDATE,REFER,INFO Reason: q.850;cause=1 Server: Cirpack/v4.42a (gw_sip) Content-Length: 0 Not really backwards compatible, we find we now must use custom with every carrier, with one we needed to set privacy header off, with others we needed to play with different headers. In the past we just clicked p asserted iddentity or remote party ID and it worked with almost all trunks. Quote Link to comment Share on other sites More sharing options...
cei66 Posted January 31, 2012 Author Report Share Posted January 31, 2012 a new log file with a OVH trunk created with 4.5 version log2.txt Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 31, 2012 Report Share Posted January 31, 2012 Hello , i ve got the problem with the second trunk who is completely create with the 4.5 version , with the same trunk created with the 4.3 version i only have to retype the password when i launch the 4.5 version and then it's ok. the log file is with : first OVH39 trunk(created with 4.3+ retype password)ok second OVH4139 trunk (created with 4.5) error Unfortunately, we have seen issues after upgrading the PBX from 4.3 to 4.5. Fortunately, it is not the end of the road The simplest way to resolve this issue is to place a call on 4.3 version, look at the SIP INVITE that is going out the trunk provider(or save the log), upgrade to 4.5, then adjust the "custom headers" to match the 4.3 behavior. Ex: Some providers want 'from' header and 'P-Asserted' header content to be same. Then you can choose the same drop-down option for both 'from' header and 'P-Asserted' headers under "custom headers" section on the trunk. Some providers do not like the Privacy header or the P-charging vector headers. You can select "Don't use this header' option. Quote Link to comment Share on other sites More sharing options...
cei66 Posted January 31, 2012 Author Report Share Posted January 31, 2012 Unfortunately, we have seen issues after upgrading the PBX from 4.3 to 4.5. Fortunately, it is not the end of the road The simplest way to resolve this issue is to place a call on 4.3 version, look at the SIP INVITE that is going out the trunk provider(or save the log), upgrade to 4.5, then adjust the "custom headers" to match the 4.3 behavior. Ex: Some providers want 'from' header and 'P-Asserted' header content to be same. Then you can choose the same drop-down option for both 'from' header and 'P-Asserted' headers under "custom headers" section on the trunk. Some providers do not like the Privacy header or the P-charging vector headers. You can select "Don't use this header' option. Thanks , is it in text based that you should custom and is it the red part # Trunk 2 in domain pbx.company.com Name: OVH 39 Type: register To: sip RegPass: ******** Direction: Disabled: false Global: false Display: 0033468621111 RegAccount: 0033411930139 RegRegistrar: sip.ovh.net RegKeep: 360 RegUser: 0033411930139 Icid: Require: OutboundProxy: 91.121.129.20 Ani: DialExtension: !([0-9]{4}$)!!t!700! Prefix: Trusted: false AcceptRedirect: false RfcRtp: false Analog: false SendEmail: UseUuid: false Ring180: true Failover: always HeaderRequestUri: {request-uri} HeaderFrom: {trunk} HeaderTo: {request-uri} HeaderPai: HeaderPpi: HeaderRpi: HeaderPrivacy: id HeaderRpiCharging: icid-value={icid-value};icid-generated-at={ip-address};orig-ioi={domain} BlockCidPrefix: Glob: RequestTimeout: Codecs: 8 CodecLock: true DtmfMode: Expires: 3600 FromUser: Tel: true TranscodeDtmf: false AssociatedAddresses: InterOffice: false DialPlan: UseEpid: false CidUpdate: Ignore18xSDP: false UserHdr: Colines: DialogPermission: Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 31, 2012 Report Share Posted January 31, 2012 Pretty much, yes, the red part. The actual tags (the variables enclosed with curly brackets) can be found here http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers Quote Link to comment Share on other sites More sharing options...
cei66 Posted February 1, 2012 Author Report Share Posted February 1, 2012 Pretty much, yes, the red part. The actual tags (the variables enclosed with curly brackets) can be found here http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers hello i would like to know which Header value the 4.3 version put : Request-URI : From: To: P-Asserted-Identity: P-Preferred-Identity: Remote-Party-ID: P-Charging-Vector: Privacy Indication: DAVID Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 1, 2012 Report Share Posted February 1, 2012 Looks like reply was not very clear. Let me try it in a different way. Run 4.3 version. Enable SIP logging Make a outbound call on the trunk in question Gather the SIP INVITE log. Now, upgrade the PBX to 4.5 Make a outbound call on the trunk in question Gather the SIP INVITE log. See what is different from v4.3 log. cleanup the differences based on http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers to match 4.3 INVITE If you still can't understand, please open a ticket with v4.3 logs, v4.5 logs and login info to the PBX Quote Link to comment Share on other sites More sharing options...
cei66 Posted February 1, 2012 Author Report Share Posted February 1, 2012 Looks like reply was not very clear. Let me try it in a different way. Run 4.3 version. Enable SIP logging Make a outbound call on the trunk in question Gather the SIP INVITE log. Now, upgrade the PBX to 4.5 Make a outbound call on the trunk in question Gather the SIP INVITE log. See what is different from v4.3 log. cleanup the differences based on http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers to match 4.3 INVITE If you still can't understand, please open a ticket with v4.3 logs, v4.5 logs and login info to the PBX Thanks with this configuration it works like in 4.3 version # Trunk 2 in domain pbx.company.com Name: OVH 39 Type: register To: sip RegPass: ******** Direction: Disabled: false Global: false Display: 0468621111 RegAccount: 0033411930139 RegRegistrar: sip.ovh.net RegKeep: 360 RegUser: 0033411930139 Icid: Require: OutboundProxy: 91.121.129.20 Ani: DialExtension: !([0-9]{4}$)!!t!700! Prefix: Trusted: false AcceptRedirect: false RfcRtp: false Analog: false SendEmail: UseUuid: false Ring180: true Failover: always HeaderRequestUri: {request-uri} HeaderFrom: {trunk} HeaderTo: {request-uri} HeaderPai: HeaderPpi: HeaderRpi: HeaderPrivacy: HeaderRpiCharging: icid-value={icid-value};icid-generated-at={ip-address};orig-ioi={domain} BlockCidPrefix: Glob: RequestTimeout: Codecs: 8 CodecLock: true DtmfMode: Expires: 3600 FromUser: Tel: true TranscodeDtmf: false AssociatedAddresses: InterOffice: false DialPlan: UseEpid: false CidUpdate: Ignore18xSDP: false UserHdr: Colines: DialogPermission: Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 2, 2012 Report Share Posted February 2, 2012 Not really helping.. Please open a ticket with v4.3 logs. 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.